Oracle® Calendar Reference Manual Release 2 (9.0.4) Part Number B10891-02 |
|
|
View PDF |
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.
uniaccessrights
- Grant access rights to agendas of users, resources or event calendars.
uniaccessrights -ls -grantee <user> -grantor <filter> [-n <node-ID>] [-host <hostname>] [[-p <psw>] [-uid <uid>] | [-krb]] [-designate] [-eventview] [-taskview] [-scheduling] uniaccessrights -mod -grantee <user> -grantor <filter> [-n <node-ID>] [-host <hostname>] [[-p <psw>] [-uid <uid>] | [-krb]] [-designate <modifier>] [-taskview <modifier>] [-eventview <modifier>] [-scheduling <modifier>] uniaccessrights -reset -grantee <user> -grantor <filter> [-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
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:
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
.
<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.
<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.
filter: <user> / [<resource>] / [<eventcal>]
Specify the entity that is granting the rights for access to its calendar. The grantor can be a user, resource or event calendar. If more than one match for the entity 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 syntax information.
<user>
Specify the user or users to whom the access rights are granted. If this is a multi-node network, specify the grantee's remote node-ID. 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
if you want 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.
<hostname>
Restrict the nodes to those on the specified host. To specify a port number use the following format for the <hostname> parameter: "hostname:port".
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.
Use automatic Kerberos login. This option cannot be used with the -p and -uid options.
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
".
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.
<node-ID>
Specify the node. Required if more than one node exists on the host. In this case, (multi-node networks) the node-ID must be the node of the grantor, and the remote node must be specified in the grantee's filter; for example:
uniaccessright -mod -grantor "R=Conference Room Saturn" -grantee "NODE-ID=2001" -n 2000 -p <sysoppassword>
<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 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.
<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.
<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.
<user-ID>
The administrator's user ID. If none is specified the SysOp is used.
Print the current version number of uniaccessrights
.
Print a usage message explaining how to run uniaccessrights
.
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.
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
Some example specifications are: "S=Kilpi/G=Eeva", "S=B*/G=Nicole/O=Acme", "O=Acme/ID=1111/OU1=authors"
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.
Key | Values |
---|---|
|
[true, false] |
|
|
|
|
|
|
Key | Values |
---|---|
|
[true, false] |
|
|
|
|
|
|
Key | Values |
---|---|
|
[true, false] |
% uniaccessrights -ls -host gravel -grantor "S=Martin/G=Don" -p sysOpPsw
% uniaccessrights -mod -grantee "S=OBrian" -grantor "S=Martin/G=Don" -host gravel -p sysop1 -eventview "PERSONAL=ALL" -taskview "all=true"
% uniaccessrights -mod -grantee "S=OBrian" -grantor "S=Martin/G=Don" -host gravel -p sysop1 -designate "CONFIDENTIALEVENT=REPLY/PUBLICEVENT=MODIFY/PERSONALEVENT=VIEWTIMES"
% 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
% uniaccessrights -mod -grantor "S=Smith/G=John/JOB-TITLE=Professor" -grantee "OU2=student" -host gravel -p sysop1 -scheduling "canbookme=false"
% uniaccessrights -mod -grantee "S=Smith/G=John" -grantor "N=Montreal Jazz Festival" -host gravel -p sysopPsw -n 24 -designate "PUBLICEVENT=MODIFY"
% uniaccessrights -ls -grantor "S=Smith/G=John" -grantee "S=*" -host gravel -p sysopPsw -n 24 -designate
% uniaccessrights -ls -grantor "S=Smith/G=John" -grantee "S=Kusuma" -host gravel -p sysopPsw -n 24 -taskview "ALL=true"
Exit values are:
0 Success
1 Failure
2 Usage error
uniaddnode
- Create a new calendar server node or re-initialize an existing one.
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
uniaddnode [-n nodeId] [-t timezone] [-a alias] [-r] [-p sysOpPWD] [-y] uniaddnode -sn StartNode -num NumberOfNodes [-p sysopPWD] [-y] uniaddnode -v uniaddnode -h
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
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.
<nodealias>
Specify an alias for the node. <nodealias> is a descriptive word which cannot contain spaces.
<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.
<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 a directory server, if no password is specified, the password is set as empty.
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.
<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".
<DmPsw>
For standalone only. 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.
<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.
<numberOfNodes>
Used with the -sn option to specify the number of node-IDs to be generated for the node initialization.
Used with the -r option to auto-confirm the re-initialization.
Print the current version number of uniaddnode
.
Print a usage message explaining how to run uniaddnode
.
% uniaddnode -n 44 -a admin -t EST5EDT -w DmPsw -p sysOpPsw uniaddnode: Database initialization done uniaddnode: node [44] has been successfuly initialized
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
$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 values are:
0 Success
Any non-zero value signals an error.
uniadmrights
- Manage the administration rights of users.
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
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:
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
.
Note: Use the ManageHolidays, ManageAdmGroups, and CreatePublicGroups keywords in the |
<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.
<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.
<rightsFilter>
Specify the event calendar administration rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.
<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".
Use automatic Kerberos login. This option cannot be used with the -p and -uid options.
List all rights granted to the specified user.
<node-ID>
Specify the node. Required if more than one node exists on the host.
<rightsFilter>
Specify the node level administration rights. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.
<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.
<rightsFilter>
Specify the public groups management rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.
<rightsFilter>
Specify the resource administration rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.
<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.
<rightsFilter>
Specify the server administration rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.
<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.
<user-ID>
The administrator's user ID. If none is specified the SysOp is used.
<rightsFilter>
Specify the user administration rights. Cannot be used with -ls. See FORMAT OF THE <rightsFilter> ARGUMENT for details on the <rightsFilter> argument.
Print the current version number of uniadmrights
.
Print a usage message explaining how to run uniadmrights
.
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.
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
Some example specifications are: "S=Kilpi/G=Eeva", "S=B*/G=Nicole/O=Acme", "O=Acme/ID=1111/OU1=authors"
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.
Key | Possible values | Description |
---|---|---|
|
|
All rights listed in this table |
|
|
Update the unison.ini file |
Key | Possible values | Description |
---|---|---|
|
|
All rights listed in this table |
|
|
Access the CSM to start and stop servers and nodes. |
% uniadmrights -ls -u "S=Smith/G=Alice" -host gravel -p psw -n 203
% uniadmrights -u "S=Martin/G=Don/OU1=r&d" -node "holiday=true" -n 80 - krb
% uniadmrights -u "S=Martin/G=Don/OU1=r&d" -n 80 - krb -scope "network"
% uniadmrights -u "S=Martin/G=Don/OU1=r&d" -user "create=true" -admgrp "create=true/delete=true" -n 80 - krb
% uniadmrights -u "S=Bean/G=Joan" -user "all=false" -host montreal -p psw
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 values are:
0 Success
1 Failure
2 Usage error
uniarch
- Create a tar archive of the calendar server.
uniarch [-d] [-y] [-t | -f <filename>] [-p <path>] [-u <user>] [-g <group>] uniarch -v uniarch -h
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.
Warning: uniarch backs up the calendar server internal database. If a directory server is being used, its database should also be backed up. |
Back up only the contents of $ORACLE_HOME/ocal/db/nodes
, the calendar server database.
<filename>
Specify the name of the archive file. If this option is not used, prompting for the filename occurs.
Force the tar default device to be used for the archive destination file.
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.
<group>
Specify the unix group.
<path>
Specify the path to the server directory which contains the db
directory (such as -p "$ORACLE_HOME/ocal"
).
<user>
Specify the unix user.
Print the current version number of uniarch
.
Print a usage message explaining how to run uniarch
.
$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
% 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 values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
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.
unib2lendian [-n <node-ID>] unib2lendian -v unib2lendian -h
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 machine, such as Windows NT.
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.
<node-ID>
Specify a node to convert. Required if more than one node exists on the local host.
Print the current version number of unib2lendian
Print a usage message explaining how to run unib2lendian
.
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.
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.
$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.
*.dat
files in the perm_conv
directory to the $ORACLE_HOME/ocal/db/nodes/
<N#>/perm
directory on the little-endian system.$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.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
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.
Exit values are:
0 Success
1 Failed to convert the database
2 Usage error
unidbfix, unistart, unistop, uninode
unicheck
- Verify the calendar server file system.
unicheck [-nowarn] [-nodb | -maxdb <n>] [-c] unicheck -v unicheck -h
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:
Any discrepancies are reported. Unless an entire file or directory is missing, any problems found are fixed by 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.
<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.
Do not print warning messages (error messages are still printed).
Do not check database files.
Computes a system-independent checksum for each static file. If this option is used, output should be redirected to a file for future use.
Print the current version number of unicheck
.
Print a usage message explaining how to run unicheck
.
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
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 values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unicksum
- Generate a checksum for a file.
unicksum <filename> unicksum -v unicksum -h
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.
Print the version number of unicksum
.
Print a usage message explaining how to run unicksum
.
unitzinfo
executable:
% unicksum unitzinfo unicksum: checksum of the file "unitzinfo" is 18187
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniclean
- Clean up the calendar server file system.
uniclean uniclean -v uniclean -h
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.
Print the current version number of uniclean
.
Print a usage message explaining how to run uniclean
.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unicheck
unicpinr
- Copy resource data from a file created by unicpoutr
to a calendar server node.
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
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.
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.
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.
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.
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.
<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.
<filename>
Specify the input file name. The file must have been created with the unicpoutr
utility. By default, standard input is used.
<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".
List the file name followed by the name of the resource it contains for each specified file name. Files not created with the unicpoutr
command are not listed. If no file names are specified, the files of the current directory (.) are examined.
<node-ID>
Specify the node.
<SysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
<day> <month> <year>
Set the start date of the events to be processed. By default, all events in the file are created; this option and the -end 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.
Print the current version number of unicpinr
.
Print a usage message explaining how to run unicpinr
.
Key | Description |
---|---|
|
Resource name |
|
Resource number |
|
Capacity |
|
Contact's surname |
|
Contact's given name |
|
Location |
|
Phone number |
|
Fax phone number |
unicpinr
is used in conjunction with unicpoutr
and uniuser
to move a resource from one node to another. In the following example, the resource "betacam" will be moved from node 30 to 35.
% uniuser -ls "R=Betacam" -n 30 R=Betacam/CA=1/ID=1234
% unicpoutr "R=Betacam" -f betacam.dat -n 30
% uniuser -del "R=Betacam" -n 30
% unicpinr -add -f betacam.dat -n 35
unicpinr
can be used in conjunction with unicpoutr
to add the agenda of one resource to that of another resource. This example adds the agenda for "PineNook" to the agenda for "OakCranny" and at the same time changes the capacity of "OakCranny" to 5.
% unicpoutr "R=PineNook" -f pinenook.dat -n 30
% vi pinenook.dat
% unicpinr -f pinenook.dat -n 30
The agenda information for PineNook has been added to the existing agenda information for OakCranny.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Depending on the size of the agenda in the file, unicpinr
may take some time to complete.
The unicp
family of utilities have the following limitations that must be considered.
From the perspective of a moved user (or resource), each of the moved events in the new agenda is a personal event with enough data in the description to determine who created the event and who the attendees are. All links are broken but there is sufficient information in the description to allow the links to be rebuilt.
Note also that where the agenda of one user (or resource) is being added to that of another, double-booking may occur.
When a user (or resource) is moved to a new node, that user (or resource) should be deleted from the old node (using uniuser -del
).
When a resource is deleted, all traces of that resource are removed. Thus, that resource is no longer booked for events.
When a user is deleted, all traces of that user are removed. Thus, that user is no longer invited to events created by other users. Furthermore, and most importantly, all events created by the user are deleted. As a consequence, any user in the old node who was invited to an event by the moved user, will no longer be able to view the event.
If several users (and/or resources) are to be moved, it is best to perform the move in three phases:
unicpoutu
and/or unicpoutr
).unicpinu
and/or unicpinr
).This ensures that information on any links among the users (and/or resources) being moved is not lost (see "Deleting a resource").
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.
unicpoutr, unicpr
unicpinu
- Copy the contents of a file of user data created by unicpoutu
to a calendar server node.
unicpinu [-add ] [-f <filename>] [-start <day> <month> <year>] [-end <day> <month> <year>] [-host <hostname>] -n <node-ID> [-p <SysOpPsw>] unicpinu [-add ] [-start <day> <month> <year>] [-end <day> <month> <year>] [-host <hostname>] -n <node-ID> [-p <SysOpPsw>] < <filename> unicpinu -ls [<filename(s)>] unicpinu -v unicpinu -h
unicpinu
copies a file containing user data (created by unicpoutu
) into a calendar server node. The utility can be used in conjunction with unicpoutu
to add the agenda of one user to that of another user (see EXAMPLES). Although it can also be used, in conjunction with unicpoutu
, to move a user from one node to another, unimvuser
is the proper utility for moving users. unimvuser
prevents the data loss that occurs when moving users with unicpoutu
and unicpinu
.
By default, the user specified in the file must already exist in the destination calendar server node. If this is not the case, they can be added using the -add option.
unicpinu
can only be run if the calendar server is up.
It is important to understand how unicpinu
handles the information in the input file during the copy into the destination node:
These are the values for the keys S, G, I, and X, and the keys OU1, OU2, OU3, OU4, O, C, A and P respectively (see NAME AND ADDRESS KEYS for details on these keys). Only non-null values are output to the file by unicpoutu
so not all keys may have a value in the file.
unicpinu
uses these values to uniquely identify an existing user in the destination node.
Personal information includes employee number, phone number, extension, fax number, job title and office mailing address.
Where the user already exists in the destination node, these values are already set and unicpinu
does NOT overwrite them with those in the input file.
Where a user already exists in the destination node, unicpinu
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 user as the owner. Where appropriate, the description of each event contains extra data indicating the users invited 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 events and completed tasks that fall within a specified range. Incomplete tasks are always imported.
Warning: Holidays are output by unicpoutu as meetings, and therefore input by unicpinu as meetings. Only the existing holidays in the destination node appear as holidays in the user's agenda. |
Add the user to the database and then copy in the user's agenda. It is an error to specify this option if the user already exists. Note that for directory servers, the user must already exist in the directory server (all of the X.400 key-value pairs specified in the input file must match), and must not already be a calendar user.
<day> <month> <year>
Set the end date for the events and tasks to be processed. By default, all events and tasks in the file are created; this option and the -start option allow you to exclude certain events and tasks. Dates must be expressed in the form "day month year". Years must be expressed 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.
<filename>
Specify the input file name. The file must be created with the unicpoutu
utility. If this option is not specified, standard input is used.
<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".
<filename(s)>
Print the filename followed by the X.400 name and address of the user contained in the file, for each specified file name. Files not created by the unicpoutu
command are not listed. If no file names are specified, the files in the current directory (.) are examined.
<node-ID>
Specify the node.
<SysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
<day> <month> <year>
Set the start date for the events and tasks to be processed. By default, all events and tasks in the file are created; this option and the -end option allow you to exclude certain events and tasks. Dates must be expressed in the form "day month year". Years must be expressed 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.
Print the current version number of unicpinu
.
Print a usage message explaining how to run unicpinu
.
unicpinu
is used in conjunction with unicpoutu
and uniuser
to move a user from one node to another. In this example the user "Sarah Herman" will be moved from node 20 to 44, and one of her organizational units changed from "Sales" to "R&D".
Warning: Use this procedure ONLY if unimvuser cannot complete the move you need to make. See WARNINGS for information on the data that is lost during this procedure. |
% uniuser -ls "S=Herman/G=S*" -n 20 S=Herman/G=Sarah/OU1=Dallas/OU2=Sales/ID=1234
% unicpoutu "G=Sara*/S=Herman -f sherman.dat -n 20
unicpinu -add
command is to succeed.
% uniuser -del "G=Sara*/S=Herman" -n 20
% unicpinu -add -f sherman.dat -n 44 S=Herman/G=Sarah/OU1=Dallas/OU2=Sales/ID=1234
unicpinu
can be used in conjunction with unicpoutu
to add one user's agenda to that of another user. This example adds Sarah Herman's agenda to Yannick Olafsen's agenda.
% unicpoutu "G=Sara*/S=Herman" -f sherman.dat -n 20
sherman.dat
file to modify the X.400 name and address to match that contained in the database for Yannick Olafsen.
% vi sherman.dat
% unicpinu -f sherman.dat -n 24
The agenda information for Sarah Herman is added to the existing agenda information for Yannick Olafsen.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Depending on the size of the agenda in the file, unicpinu
may take some time to complete.
The unicp
family of utilities have the following limitations that must be considered.
From the perspective of a moved user (or resource), each of the moved events in the new agenda is a personal event with enough data in the description to determine who created the event and who the attendees are. All links are broken but there is sufficient information in the description to allow the links to be rebuilt.
Note also that where the agenda of one user (or resource) is being added to that of another, double-booking may occur.
When a user (or resource) is moved to a new node, that user (or resource) should be deleted from the old node (using uniuser -del
).
When a resource is deleted, all traces of that resource are removed. Thus, that resource is no longer booked for events.
When a user is deleted, all traces of that user are removed. Thus, that user is no longer in the list of invited users of events created by other users. Furthermore, and most importantly, all events created by the user are deleted. As a consequence, any user in the old node who was invited to an event by the moved user, will no longer be able to view the event.
If several users (and/or resources) are to be moved, it is best to perform the move in three phases:
unicpoutu
and/or unicpoutr
).unicpinu
and/or unicpinr
).This ensures that information on any links among the users (and/or resources) being moved is not lost (see "Deleting a user (or resource)").
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.
unicpoutu, unicpu
unicpoutr
- Copy resource data from a calendar server node into a file.
unicpoutr -u resname [-f <filename>] [-host <hostname>] [-start <day> <month> <year>] [-end <day> <month> <year>] -n <node-ID> [-p <SysOpPsw>] unicpoutr -v unicpoutr -h
unicpoutr
copies a resource's data from a calendar server node to a file. It can be used in conjunction with the unicpinr
utility to move a resource from one node to another as well as to copy the resource agenda from one resource to another.
unicpoutr
can only be run if the calendar server is up.
unicpoutr
copies the following information to the file (see unicpr
for more information concerning the format and content of the output file):
Agenda information includes the past and future events either owned by the resource or to which the resource is invited. The -start and -end options may be used to export those events with an attendance record which falls within a specified time period.
The following information is NOT copied to the file:
<day> <month> <year>
Set the end date of the events to be processed. By default, all events are output; 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.
<filename>
Specify the output file name. The file must not exist. By default, the standard output is used.
<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".
<node-ID>
Specify the node.
<sysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
<day> <month> <year>
Set the start date of the events to be processed. By default, all events are output; this option and the -end 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.
<res>
Used to specify a resource. The res
argument must match a single resource or an error is reported. See FORMAT OF THE res ARGUMENT for details on how to specify this argument.
Print the current version number of unicpoutr
.
Print a message explaining how to run unicpoutr
.
The res 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. "R=betacam\/loaner/S=Khupfer".
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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note that if the ID key-value pair is specified in the res argument, all other key-value pairs specified along with it are ignored.
Key | Field |
---|---|
|
Resource name |
|
Resource number |
|
Capacity |
|
Contact's surname |
|
Contact's given name |
|
Identifier |
|
Resource unique identifier |
|
Location |
|
Phone number |
|
Fax phone number |
kitchen.dat
:
% unicpoutr "R=Kitchen" -f kitchen.dat -n 20
% unicpoutr "R=Kitchen" -f kitchen.dat -start 10 1 1998 -n 20
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Depending on the size of the agenda, unicpoutr
may take some time to complete.
The unicp
family of utilities have the following limitations that must be considered.
From the perspective of a moved user (or resource), each of the moved events in the new agenda is a personal event with enough data in the description to determine who created the event and who the attendees are. All links are broken but there is sufficient information in the description to allow the links to be rebuilt.
Note also that where the agenda of one user (or resource) is being added to that of another, double-booking may occur.
When a user (or resource) is moved to a new node, that user (or resource) should be deleted from the old node (using uniuser -del
).
When a resource is deleted, all traces of that resource are removed. Thus, that resource is no longer booked for events.
When a user is deleted, all traces of that user are removed. Thus, that user is no longer invited to events created by other users. Furthermore, and most importantly, all events created by the user are deleted. As a consequence, any user in the old node who was invited to an event by the moved user will no longer be able to view the event.
If several users (and/or resources) are to be moved, it is best to perform the move in three phases:
unicpoutu
and/or unicpoutr
).unicpinu
and/or unicpinr
).This ensures that information on any links among the users (and/or resources) being moved is not lost (see "Deleting a user (or resource)").
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.
unicpinr, unicpr
unicpoutu
- Copy user data from a calendar server node to a file.
unicpoutu -u username [-f <filename>] [-host <hostname>] [-start <day> <month> <year>] [-end <day> <month> <year>] [-holiday] -n <node-ID> [-p <SysOpPsw>] unicpoutu -v unicpoutu -h
unicpoutu
copies a user's data from a calendar server node to a file. It can be used in conjunction with the unicpinu
utility to copy an agenda from one user to another. Although it can also be used, in conjunction with unicpinu
, to move a user from one node to another, unimvuser
is the proper utility for moving users. unimvuser
prevents the data loss that occurs when moving users with unicpoutu
and unicpinu
.
unicpoutu
can only be run if the calendar server is up.
unicpoutu
copies the following information to the file (see unicpu
for more information concerning the format and content of the output file):
This includes the past and future events either owned by the user or to which the user is invited. Holiday events are not included unless the -holiday option is used. The -start and -end options may be used to export events falling within a specified time period.
Also included are all incomplete tasks and, by default, all completed tasks. The -start and -end options may be used to export completed tasks falling within a specified time period.
The following information is NOT copied to the file:
<day> <month> <year>
Set the end date of the events and tasks to be processed. By default, all events and tasks are output; this option and the -start option allow you to exclude certain events and tasks. Dates must be expressed in "day month year" form. 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.
<filename>
Specify the output file name. The file must not exist. By default, standard output is used.
Include the holidays from the user's agenda in the output file. Holidays are output as meetings, with all users in the node included as attendees to the meeting. If the user's agenda is subsequently input into a new node using unicpinu
, only the existing holidays in the new node appear as holidays in the user's agenda; the holidays from the old node appear as meetings.
<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".
<node-ID>
Specify the node.
<sysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
<day> <month> <year>
Set the start date of the events and tasks to be processed. By default, all events and tasks are output; this option and the -end option allow you to exclude certain events and tasks. Dates must be expressed in "day month year" form. 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.
<user>
Used to specify a user. The user argument must match a single user or an error is reported. See FORMAT OF THE user ARGUMENT for details on how to specify this argument.
Print the current version number of unicpoutu
.
Print a usage message explaining how to run unicpoutu
.
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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
% unicpoutu -u "S=Herman/G=Sa*" -f sherman.dat -n 20
unicpoutu -u "S=Herman/G=Sa*" -f sherman.dat -start 10 1 1998 -n 20
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Depending on the size of the agenda, unicpoutu
may take some time to complete.
The unicp
family of utilities have the following limitations that must be considered.
From the perspective of a moved user (or resource), each of the moved events in the new agenda is a personal event with enough data in the description to determine who created the event and who the attendees are. All links are broken but there is sufficient information in the description to allow the links to be rebuilt.
Note also that where the agenda of one user (or resource) is being added to that of another, double-booking may occur.
When a user (or resource) is moved to a new node, that user (or resource) should be deleted from the old node (using uniuser -del
).
When a resource is deleted, all traces of that resource are removed. Thus, that resource is no longer booked for events.
When a user is deleted, all traces of that user are removed. Thus, that user is no longer listed in the attendee lists of events created by other users. Furthermore, and most importantly, all events created by the user are deleted. As a consequence, any user in the old node who was invited to an event by the moved user will no longer be able to view the event.
If several users (and/or resources) are to be moved, it is best to perform the move in three phases:
unicpoutu
and/or unicpoutr
).unicpinu
and/or unicpinr
).This ensures that information on any links among the users (and/or resources) being moved is not lost (see "Deleting a user (or resource)").
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.
unicpinu
, unicpu
unicpr
- Format of the file the unicpoutr
utility creates, and the unicpinr
utility reads.
The unicpoutr
utility creates, and the unicpinr
utility reads, an ASCII file with the following format.
{ <resource identification> } K Events: <event descriptions>
Except for the open brace bracket and close brace bracket which respectively open and close the <resource identification> section of the file, each line of the file begins with a single character code which defines the data stored on that line. A space follows the single character code. The unicpinr
utility ignores blank lines and lines beginning with unknown codes.
Codes in the <resource identification> section are not legal in the <event descriptions> section, and vice versa.
The following describes the lines that the <resource identification> section may contain.
The following describes the lines that the <event descriptions> section may contain.
{ F Unison Export File V A.04.00 E FALSE X S=Baker/G=James R a Kitchen R b 12 R c 10 R d (123)-456-7890 R e 217 R f (123)-456-7891 I Password P 4 480 1140 1 15 127 2 0 15 0 0 0 #These define display and notification preferences as follows: # 4 ShowEventTitles # 480 StartDay at 8:00am # 1140 EndDay at 7:00pm # 1 StartWeek display on Sunday # 15 Display in time increments of 15 min. # 127 Display all days Sunday to Saturday # 2 Display time in am/pm format # 0 Periodic refresh disabled # 15 Refresh frequency 15 minutes # 0 Mail notification disabled # 0 No reminders # 0 No lead time before reminders N 1 } K Events: S 2262975 D 75 T Lunch G Kitchen I 0 R N0 M Kitchen W Kitchen A TRUE 1 5 C Lunch time C David Robinson C Kathy Bates O
unicpinr(8), unicpoutr(8).
unicpu
- File format of the file the unicpoutu
utility creates, and the unicpinu
utility reads.
The unicpoutu
utility creates, and the unicpinu
utility reads, an ASCII file with the following format.
{ <user identification> } K Events: <event descriptions> K Tasks: <task descriptions>
Except for the open brace bracket and close brace bracket which respectively open and close the <user identification> section of the file, each line of the file begins with a single character code which defines the data stored on that line. A space follows the single character code. The unicpinu
utility ignores blank lines and lines beginning with unknown codes.
Codes in the <user identification> are not legal in either of the other two sections, and vice versa.
The following describes the lines that the <user identification> section may contain.
The following describes the lines that the <event descriptions> section may contain.
The following describes the lines that the <task descriptions> section may contain.
{ F Unison Export File V A.02.51 E FALSE X S=Baker/G=James/I=T/OU1=Labs/OU2=SysAdmin U a Calendar Server Corporation, U a 1234 Software Blvd., U a Suite 999, U a Software Valley, CA 99999. U b 12 U c (123)-456-7890 U d (123)-456-7891 U e 215 U f System Administrator I Password P 4 480 1140 1 15 127 2 0 15 0 0 0 #These define display and notification preferences as follows: # 4 ShowEventTitles # 480 StartDay at 8:00am # 1140 EndDay at 7:00pm # 1 StartWeek display on Sunday # 15 Display in time increments of 15 min. # 127 Display all days Sunday to Saturday # 2 Display time in am/pm format # 0 Periodic refresh disabled # 15 Refresh frequency 15 minutes # 0 Mail notification disabled # 0 No reminders # 0 No lead time before reminders N 2 1 } K Events: S 2262975 D 75 T Friday R&D meeting G Conference Room I 0 R N0 M Baker James W Baker James A TRUE 1 5 C Discuss next week's activities. C James Baker C David Robinson C Kathy Bates O S D=25/Y=2000/M=April/T=00:00/z=EST5EDT D 1440 T Company Holiday I 1 R A2 M Robinson David W Robinson David A TRUE 0 0 O K Tasks: S D=1/Y=2000/M=April/T=8:00/z=EST5EDT D D=30/Y=2000/M=April/T=17:00/z=EST5EDT T System Overhaul. R 3 L 70 M Baker James W Baker James C Upgrade OS version from A.02.50 to A.04.51 O
unicpinu(8), unicpoutu(8)
unidb2ldif
- Export a calendar server node to an LDIF file. This utility is not available with an Oracle Internet Directory Server installation. It is intended to be used with the stand alone calendar server installation.
unidb2ldif -n <node-ID> [-host <hostname>] [-p <sysOpPsw>] [-u <user>] unidb2ldif -v unidb2ldif -h
unidb2ldif
exports the database of a specific calendar server node into an LDIF files: node
<node-ID>.ldif
. This file contains a series of modifications in the form of change records. The ldapmodify
utility can use this file to populate a new directory server, and to add new entries to or modify existing entries in a pre-populated directory server.
Where a directory server is already in place, unidb2ldif
checks the information in the directory server with what it finds in the calendar server node to determine what to output to the LDIF files (i.e. whether an entry would need to be added to the directory server, or, if it already existed in the directory server, whether modifications to it would be required.
This utility does not work with the Oracle Internet Directory Server which is part of the Oracle Collaboration Suite. It is intended to be used with the stand alone calendar server installation.
<node-ID>
Specify the node to be exported.
<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".
<sysOpPsw>
Provide the SYOSP password of the node. If this option is not used, prompting for it occurs.
<user>
Specify the user, resource or event calendar account to export. See FORMAT OF THE <user> ARGUMENT for details on how to specify <user>.
Print the current version number of unidb2ldif
.
Print a usage message explaining how to run unidb2ldif
.
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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note: If the ID key-value pair is specified for specifying a user in the <user> argument, all other key-value pairs specified along with it are ignored. |
Key | X.400 Field |
---|---|
N |
Event calendar name |
Key | X.400 Field |
---|---|
|
Resource name |
|
Resource number |
|
Resource unique identifier |
unidb2ldif.ini
The [UNIDB2LDIF]
and [LDAP]
sections of this file contain a number of parameters used by unidb2ldif
.
[UNIDB2LDIF]
ldifdir =
<directory>
Specify the output directory for LDIF files. The default is <calendar_install_path>/tmp
.
userfilterfmt =
"(uid=%UID%)
"
Specify the LDAP search filter format to be used to match existing entries. By default, the User ID is used. Supported format codes are:
[LDAP]
host =
<hostname>
Specify the host on which the directory server is running. Should be specified when migrating to an existing directory server installation.
port =
<portnumber>
Specify an alternate TCP port on which the directory server is running. The default port is 389.
basedn =
<dn>
Specify the starting point for search operations on the Directory Information Tree. This is also the base distinguished name used to create new directory entries, unless the -dnsuffix option is used.
binddn =
<dn>
Specify the distinguished name used to bind to the directory server.
bindpwd =
<password>
Specify the password used to bind to the directory server.
admin =
<dncomponent>
Use in conjunction with baseDN
to specify the location of the calendar server administrators in the Directory Information Tree.
admingroup =
<dncomponent>
Use in conjunction with baseDN
to specify the location of the calendar server administrators' group in the Directory Information Tree.
defaultpwd =
<password>
Default user password to use for new calendar server users and resources that are created. The default password is "sesame".
$ORACLE_HOME/ocal/log/unidb2ldif.log
A log file of all related errors and warnings.
$ORACLE_HOME/ocal/tmp/node<node-ID>.ldif
LDIF file describing a series of modifications in the form of change records.
"Surname" is a required attribute for the inetOrgPerson
object class. Items without an assigned value for "Surname" have "Surname" initialized to "CalUser:".
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unidbbackup
- Create an archive of a calendar server node and related configuration information.
unidbbackup -d <dst> [-n <nodes>] [-blocking] [-lockall] unidbbackup -v unidbbackup -h
unidbbackup
creates a backup of a calendar server's nodes and its related configuration information. More specifically, it creates a backup of the $ORACLE_HOME/ocal/misc
directory and the $ORACLE_HOME/ocal/db
directory. As the information in these two directories is interrelated, it is important to ensure they are backed up at the same time.
unidbrestore
is the complementary utility to unidbbackup
. By default, these utilities perform a copy of the source to the destination. If behavior other than a straight copy is needed, an alternate backup/restore command can be specified using the [UTL] external_backup
and external_restore
parameters in the unison.ini
file. See FILES for details on how to specify an alternate backup command.
unidbbackup
can be run when the calendar server is either up or down.
Warning: unidbbackup backs up the calendar server internal database. If a directory server is being used, its database should also be backed up. |
Perform the backup in read locking mode. This lock will accept all consecutive read until it encounters the first write. Then it will queue all read and write afterwards. Users will not be able to use their calendar while the backup is performed using this option. This option should be used for very fast backups only.
<dst>
Specify the destination for the archive, where <dst> is a directory name.
Lock all the specified nodes at the same time instead of one by one. This will improve the data consistency for connected nodes.
<nodes>
Specify which nodes to backup. The format of <nodes> is a simple list of node numbers separated by commas: "-n 102,103,104
" (no blanks between node numbers). Id none are specified, all nodes will be backed up.
Print the current version number of unidbbackup
.
Print a usage message explaining how to run unidbbackup
.
/backups/cserver/jan.7.99
:
% unidbbackup -d /backups/cserver/jan.7.99 - n 102,104
Exit values are:
0 Success
Any non-zero value signals an error
$ORACLE_HOME/ocal/misc/unison.ini
The following keys in the [UTL]
section of this file are of relevance to this utility:
lock_timeout
This key sets the time-out, in seconds, for the lock operation on the database.
backupatonce
This key is used in combination with the external_backup
parameter. When set to TRUE
, the alternate backup defined by external_backup
is called once. When set to FALSE
, the alternate backup is called for each node database directory and for the misc
directory.
backup_timeout
This key sets the time-out, in seconds, for the backup operation on the database.
external_backup
This key provides a way for an alternate backup utility to be invoked by unidbbackup
. unidbbackup
uses the value of this key, along with the arguments supplied to unidbbackup
on the command line, to construct (and subsequently invoke) the following command line:
value_of_external_backup [-f] -s <src> -d <dst>
where:
unidbbackup
constructs this from the <dst> argument specified by the user on the unidbbackup
command line)unidbbackup
constructs this argument based on the information it finds in the $ORACLE_HOME/ocal/misc/unison.ini
file)unidbbackup
iteratively invokes the generated command line until all of the required database files are backed up, locking and unlocking the database for each iteration.
The administrator must ensure that the generated command line is in fact a valid one for the alternate utility. It may be that an intermediate utility is required to take this command line, create one which is valid, and then invoke it. In this case, external_backup
would be set to invoke the intermediate utility.
The accepted value for external_backup
is any command line. There is no assigned default value for this key.
unidbrestore
unidbconv
- Convert a version 2.62 node database to version 6.00.
unidbconv -n <node-ID> | all [-kp <numpages>] [-x] [-d <directory>] unidbconv -v unidbconv -h
unidbconv
converts a version 2.62 node database to version 6.00. In general you do not invoke this utility directly (a conversion is done automatically during the upgrade to a newer version of the calendar server). The last two digits of the "version" parameter in the [<YOURNODEID>] section of the unison.ini
file indicate the version of the node.
Warning: You should back up the calendar server before invoking unidbconv as this utility overwrites the existing database. |
The calendar server must be down to run unidbconv
.
In the database's Misc
directory, you need to have a file named state.ini
that contains a section named [SETUP]
and at least one blank line. Data on the conversion process will be written to this file so that the conversion can be resumed in case of a failure.
<directory>
Specify the temporary directory to be used for the conversion. The directory must exist. By default, a directory named New
will be used; this directory is found at the same level as Misc
.
<node-ID> | all
Perform the conversion on the specified node only (if <node-ID> is used) or on all nodes (if all
is used).
<numpages>
Specify the number of cache pages to use for scanning and rebuilding key files. If this option is not used, the default value of 32000 is used instead.
Turn off progress indicator.
Print the version number of unidbconv
.
Print a usage message explaining how to run unidbconv
.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unidbfix
- Check, repair, defragment and maintain a calendar server node database.
unidbfix -c [-pix|-pi] -n <node-ID> | all [-r] [-kp <numpage>] [-level [basic|full]] unidbfix -f [-pix|-pi] -n <node-ID> | all [-r] [-y] [-kp <numpage>] [-level [basic|full]] unidbfix -d [-pix|-pi] -n <node-ID> | all [-r] [-y] [-kp <numpage>] [-level [basic|full]] unidbfix -export [-pix|-pi] -n <node-ID> | all [-r] [-kp <numpage>] unidbfix -import [-pix|-pi] -n <node-ID> | all [-r] [-y] [-kp <numpage>] unidbfix -ck -n <node-ID> | all [-r] [-y] [-kp <numpage>] unidbfix -k -n <node-ID> | all [-r] [-y] [-kp <numpage>] unidbfix -i [-pix|-pi] -n <node-ID> | all [-r] [-kp <numpage>] unidbfix -v unidbfix -h
unidbfix
checks for and repairs database corruptions and/or inconsistencies, and/or defragments and compresses a node database. You should run unidbfix
as part of a regular database maintenance program.
unidbfix
carries out checks and repairs on the following parts of the database of the specified node:
unidbfix
runs in one of eight different modes as listed. If, in any mode, unidbfix
makes a fix, it reports that fix. The scan phases for each mode appear in the order in which they occur. See the NOTES section for additional information on the Remote Nodes, Bins, and File Fragmentation scan phases.
unidbfix
can be run in check mode while the calendar server is running. During a unidbfix -c
, the server will only accept read requests (including users logging on and logging off).
For the check and fix modes there are two levels of operation: basic and full. The level is specified using the -level
option. basic
is the default. The level controls which database checks are done. The basic level only checks for the most common errors, while the full level checks for more errors. As a result the basic mode is much faster than the full level.
You can run multiple instances of unidbfix -c
, each instance must be run on a different node. You can run a full unidbfix on a stopped node while the rest of the nodes are active. See unistop
to know how to stop a node.
Use uninode
, not unidbfix -import
, to administer the node network. Use unidbfix
with the -import
option only to fix corruptions in the remote node connection information in the database.
You can run unidbfix -export
while the calendar server is running.
Run in check mode. unidbfix
reports all database corruptions and inconsistencies but takes no action to correct them (use fix mode to do this). If unidbfix
detects an error, it stops the check after the scan phase in which it finds the errors. For instance, if it discovers an error during the File Sizes scan phase, it terminates on completion of this scan phase. It does not proceed to the Nodes scan phase.
Run in check key mode. Checks only the key files of the database.
Run in defragment mode. In this mode unidbfix
frees space occupied by deleted records. To ensure database consistency, unidbfix
checks the database for errors and fixes any it finds before it proceeds with defragmentation.
Warning: While it is possible to interrupt unidbfix during the defragmentation phase using a kill -9, this causes irreversible damage to the database. |
Run in export mode. In export mode unidbfix
writes remote node information from the database to the remotenode.ini
file. Note that it writes only the non-null fields for each remote node to the file. See the REMOTE NODES SCAN PHASE note for an example of how to use the -export mode.
Run in fix mode. Fix and clean up the database. This fixes all errors detected in check mode. In some circumstances unidbfix
may be forced to delete data (e.g. where corruption to the data is such that unidbfix
is unable to repair it, or where orphan data cannot be safely re-integrated).
Run in info mode. In this mode unidbfix
outputs various database statistics to the dbfix.log
file.
Run in import mode. In import mode unidbfix
writes remote node information from the remotenode.ini
file to the database. See the REMOTE NODES SCAN PHASE note for an example of how to use the -import mode as well as warnings on its use.
Run in fix key mode. Rebuilds only the key files of the database.
<numpage>
Specifies the number of cache pages to use for scanning and rebuilding key files. If this option is not used, the default value of 32000 is used instead. Larger values may significantly increase key scanning and rebuilding performance.
basic
| full
Specify the level for check and fix modes. Basic is the default level and is faster and checks for the most common errors. The full
level is slower and checks for more errors.
<node-ID> | all
Specify the node to check/fix/defragment or on which to build/scan key files. Use -n all
to scan all the nodes on a computer.
Turn on the progress indicator. By default, the progress indicator is off.
Turn off the progress indicator. By default, the progress indicator is off.
Overwrite the $ORACLE_HOME/ocal/log/dbfix.log
log file, rather than append output to it.
Turn fix and defragmentation confirmation message off.
Print the current version number of unidbfix.
Print a usage message, and a short description of each option.
% unidbfix -c -n 35
% unidbfix -f -n 12
unidbfix -c -level full -n 567
% unidbfix -d -n 10 -r
$ORACLE_HOME/ocal/log/dbfix-node-x.log
The "x" in the file name will be replaced by the node number. If "unidbfix -n all
" is used, the file name will be $ORACLE_HOME/ocal/log/dbfix-node-all.log. unidbfix
writes any errors it finds and/or any fixes it makes, to this file. It lists each error as a DATABASE ERROR, and each repair as a Fix. unidbfix
can repair any database error it finds. Totals of all errors found, fixes made, and records deleted during fixing, appear at the end of the file. Note that the total number of database errors need not equal the total number of fixes. You do not normally need to consult this file.
$ORACLE_HOME/ocal/log/unison.ini
Consult this file for a listing of all local nodes, with their corresponding directory names and node-IDs.
remotenode.ini
unidbfix
uses this file in import and export modes. It creates this file in a node's perm
directory the first time it runs on the node. The file contains a listing of all the remote node records and their data fields. The information for each remote node is as follows:
[Node-ID] RN_NUMCONNECT: any number zero and above RN_ACCESSMETHOD: must be 2 RN_SERVICENAME: must be "unieng" RN_HOSTNAME: name of the remote host
Node-ID is the remote node identification number. It must be enclosed in square brackets and it must start a line. A field can have a null value. If any field has an invalid value, unidbfix
returns an error message, and does not make the change for the remote node with the error.
The following sample remotenode.ini
file contains two remote nodes: the first has the node-ID 730 and the name "NewYork"; the second has the node-ID 631 and the name "LosAngeles".
[730] RN_NUMCONNECT = 2 RN_ACCESSMETHOD = 2 RN_SERVICENAME = "unieng" RN_HOSTNAME = "NewYork" [631] RN_NUMCONNECT = 2 RN_ACCESSMETHOD = 2 RN_SERVICENAME = "unieng" RN_HOSTNAME = "LosAngeles" unidbfix.lck
This is a lock file which prevents multiple instances of unidbfix
from running on the same node simultaneously. unidbfix
creates this in the perm
directory of the node on which it is running. In the event that a kill -9 or a system crash prevents unidbfix
from running to completion, this file remains in place. It may be manually deleted.
Exit values are:
0 Success
No errors found (check mode)
Errors found but fixed (fix mode)
Successfully defragmented (defragment mode)
Successful import (import mode)
Successful export (export mode)
1 Errors Found
Errors were found (check mode)
2 Usage error
3 User interrupt
4 Aborted
Another instance of unidbfix
was running on the node.
5 Stopped
unidbfix
either found errors in the remote node records while in fix or check mode, or it could not find the remotenode.ini
file. It needed more information to be able to continue checking or fixing.
Note that unidbfix
rebuilds the key files of the database in fix, defragment, import, and fix key modes. If unidbfix
is interrupted during any of these modes, the key files may have been deleted and not yet rebuilt. For this reason, it is highly recommended that you run unidbfix
again after an interruption.
In the Bins, Key build and File Fragmentation scan phases, unidbfix
rebuilds files without checking for, or reporting, previously existing errors. In all other scan phases all errors reported in check mode are reported in fix mode before being fixed.
For this scan phase to run, the node's remotenode.ini
must exist, and its contents must agree with the list of remote nodes in the database. When one of these conditions is not met, you can use the -export and -import modes to rectify the situation. The explanations that follow use the node-ID "43".
emotenode.ini
file does not exist for node 43. In this case, generate one from the remote node list in the database:
% unidbfix -export -n 43
remotenode.ini
file for node 43. In this case, rectify the discrepancy as follows.
First write the remote node information from the database to the remotenode.ini
file for node 43:
% unidbfix -export -n 43
Make any required edits to the resulting remotenode.ini
file.
Update the database with the modified file:
% unidbfix -import -n 43
unistart, unistop, uninode, unirndel
unidbrestore
- Restore a calendar server node and configuration information from a backup created by unidbbackup
.
unidbrestore -s <src> [-d <dst>] [-n <node-ID>] [-nomisc] unidbrestore -v unidbrestore -h
unidbrestore -
restores the node and configuration information of a calendar server from a backup created by unidbbackup
.
unidbbackup
is the complementary utility to unidbrestore
. By default, these utilities perform a copy of the source to the destination. If behavior other than a straight copy is needed, an alternate backup/restore command can be specified using the [UTL] external_backup
and external_restore
parameters in the unison.ini
file. See FILES for details on how to specify an alternate restore command.
unidbrestore
can only be run when the calendar server is down.
<dst>
Specify the destination for the restore. By default this is the $ORACLE_HOME/ocal
directory.
<node-ID>
Specify a node to restore.
Do not restore the /misc
directory.
<src>
Specify the backup source, where <src> is a directory name.
Print the current version number of unidbrestore
.
Print a usage message explaining how to run unidbrestore
.
/backups/cserver/jan.7.99
to the directory $ORACLE_HOME/ocal
:
% unidbrestore -s /backups/cserver/jan.7.99 -n 45
Exit values are:
0 Success
Any non-zero value signals an error
$ORACLE_HOME/ocal/misc/unison.ini
The following parameters in the [UTL]
section are of relevance to this utility:
lock_timeout
This parameter sets the time-out, in seconds, for the lock operation on the database.
restore_timeout
This parameter sets the time-out, in seconds, for the restore operation on the database.
external_restore
This parameter provides a way for an alternate restore utility to be invoked by unidbrestore. unidbrestore
uses the value of this parameter, along with the arguments supplied to unidbrestore
on the command line, to construct (and subsequently invoke) the following command line:
value_of_external_restore [-f] -s
<src> -d
<dst>
where
-d
<dst> specifies the destination for the restore (unidbrestore
constructs this from the dst argument supplied on the unidbrestore
command or if no argument was supplied, uses the default)-s
<src> specifies the source to be restored (unidbrestore constructs this from the src
argument supplied on the unidbrestore command line)-f
indicates that the source is a file (absence of this flag indicates the source is a directory)unidbrestore
iteratively invokes the generated command line until all of the required database files are restored, locking and unlocking the database for each iteration.
It is up to the user to ensure that the generated command line is in fact a valid one for the alternate utility. It may be that an intermediate utility is required to take this command line, create one which is valid, and then invoke it. In this case, "external_restore
" would be set to invoke the intermediate utility.
The accepted value for "external_restore
" is any command line. There is no assigned default value for this key.
unidbbackup
unidsacisetup
- Set the access control information in the directory server for the calendar server ADMIN group. This utility is not available with an Oracle Internet Directory Server installation. It is intended to be used with the stand alone calendar server installation.
unidsacisetup [-w <mgrDnPwd>] unidsacisetup -info unidsacisetup -v unidsacisetup -h
unidsacisetup
sets the directory server access control information (ACI) for the calendar server ADMIN group. Although you can use directory server utilities to set ACIs, it is advisable to use unidsacisetup
to ensure the ACI for the ADMIN group is properly set. Most calendar server utilities do not run unless the ACI for the ADMIN group is set.
This utility should be run every time a new calendar server ADMIN group is created, i.e. every time the [LDAP] admingroup
parameter in the unison.ini
file is changed.
unidsacisetup
runs whether the calendar server is up or down. The directory server, however, must be running.
This utility does not work with the Oracle Internet Directory Server which is part of the Oracle Collaboration Suite. It is intended to be used with a third party directory server in a stand alone calendar server installation.
Display the list of directory servers for which this utility can create access control information.
<mgrDnPwd>
Provide the directory server manager password (this is the password associated with the [LDAP] mgrdn
parameter in unison.ini
). If this option is not used, unidsacisetup
prompts the user for the password.
Print the version number of unidsacisetup
.
Print a usage message explaining how to run unidsacisetup
.
unidsacisetup
can set ACI:
% unidsacisetup -info
% unidsacisetup
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unidsdiff
- Find and delete differences between a calendar server node and a directory server.
unidsdiff [-n <node-ID>] [-host <hostname>] [-p <SysOpPsw>] [-d] [-y] [-verbose] [-w <password>] unidsdiff -v unidsdiff -h
This utility finds all users, resources and event calendar accounts in a calendar server node without a match in the directory server and vice versa. By default, it only reports discrepancies. Use the -d option to delete discrepancies.
The calendar server assigns each account (user, resource or event calendar) a unique identifier called an xItemId
. Unidsdiff
first checks that each xItemId
(for the specified node) in the directory server:
If unidsdiff
detects an xItemId
which does not pass one of these checks, it aborts; directory server utilities must be used to correct the problem. Otherwise unidsdiff
proceeds to verify that:
The calendar server must be up to run unidsdiff
.
Delete the differences found. The user is prompted to confirm each deletion. Without the -d option, unidsdiff
simply lists the differences.
<hostname>
Specify the host to connect to. Required if host is remote. To specify a port number use the following format for the hostname parameter: "hostname:port".
<node-ID>
Specify a node. Required if more than one exists.
Auto-confirm the deletion of any calendar or directory entry when you use the -d option.
<SysOpPsw>
Provide the calendar server SYSOP password.
Display all Distinguished Names in the directory associated with the node.
<password>
Provide the directory server manager password (this is the password associated with the [LDAP] mgrdn
parameter in unison.ini
). This is an optional parameter that you should use if the number of users in a node is larger than the directory size limit.
Print the current version number of unidsdiff
.
Print a usage message explaining how to run unidsdiff
.
unidsdiff
on node 10:
% unidsdiff -n 10 -host inkpen Enter SYSOP password: unidsdiff: detected 0 duplicate "ctCalXItemId" attributes in directory unidsdiff: detected 0 multi-valued "ctCalXItemId" attributes in directory unidsdiff: detected 0 badly-formed "ctCalXItemId" attributes in directory unidsdiff: detected 0 calendar-stores without a matching directory entry unidsdiff: detected 0 calendar directory entries without a matching calendar-store
In this case, no discrepancies were found between the directory server and the calendar server. A verbose version of the same command would result in the following output:
% unidsdiff -n 10 -host inkpen -verbose Enter SYSOP password: DN="cn=Lorde Audre,o=Acme,c=us"<ctCalXItemID010:00346> DN="cn=Kilpi Eeva,o=Acme,c=us"<ctCalXItemID010:00347> : : DN="cn=Cohen Leonard,o=Acme,c=us"<ctCalXItemID010:00484> DN="cn=Atwood Margaret,o=Acme,c=us"<ctCalXItemID010:00485> DN="cn=Brossard Nicole,o=Acme,c=us"<ctCalXItemID010:00486> unidsdiff: detected 0 duplicate "ctCalXItemId" attributes in directory unidsdiff: detected 0 multi-valued "ctCalXItemId" attributes in directory unidsdiff: detected 0 badly-formed "ctCalXItemId" attributes in directory unidsdiff: detected 0 calendar-stores without a matching directory entry unidsdiff: detected 0 calendar directory entries without a matching calendar-store
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
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.
unidssearch
- List all users in a directory server who are not calendar users.
unidssearch [-f <LDAPfilter>] [-c <numDN>] unidssearch -v unidssearch -h
unidssearch
lists all users in the directory server who are not calendar users. The output of this command may be redirected to a file, modified as needed, and subsequently used as input to uniuser
(using the -ex option). See OUTPUT FORMAT for information on the format of the file output by unidssearch
.
The calendar server must be up to run unidssearch
.
<LDAPfilter>
Specify a raw LDAP filter to combine ("AND") with the default filter to retrieve users from an LDAP directory. Refer to your directory server documentation for exact attributes that can be specified in the LDAP filter. The values specified in the filter must be in the configured character set of the directory server (e.g. UTF-8, T.61). The default filter is:
[&(objectClass=organizationalPerson)(|(!(ctCalXItemId=*)) (!(ctCalXItemId=*:*)))]
<numDN>
Limit the number of results returned to this number.
Print the current version number of unidssearch
.
Print a usage message explaining how to run unidssearch
.
The content of the file output by unidssearch
has the following format:
A did=cn=jdoe, o=Acme, c=US A did=cn=confroom4, o=Acme, c=US
Each entry has an initial "A
" character, followed by a "did
". The "A
" flags the user as one to add to the directory server as a calendar user. The "did
" is the Directory ID or Distinguished Name of the user, uniquely identifying that user in the Directory Server.
The format of this file is the same as that required for the input file to the uniuser -ex
command. If this is the intended use of the file, additional user data may be appended to the "did
", in X.400 format. For example:
A did=cn=jdoe, o=Acme, c=US/G=John/OU=Sales
% unidssearch > dsonly.txt
% unidssearch -c 50
% unidssearch -f "(sn=Smith*)"
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 values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniuser
unidssync
- Synchronize the information in a calendar server node with that in a directory server or refresh the Global Address List (GAL).
unidssync -u <user> [-remote] [-n <node-ID>] [-host <hostname>] [-p <SysOpPsw>] unidssync -galrefresh [-n <node-ID>] [-host <hostname>] [-p <SysOpPsw>] unidssync -v unidssync -h
unidssync
is only used when connected to an external directory server. This utility synchronizes the information in a calendar server node with that in the directory server. Use the -u option to synchronize a single user, resource or event calendar account.
unidssync
should be run when other applications using the directory server have changed directory server entries without the knowledge of the calendar server.
This condition might allow discrepancies to arise between the information in the internal store of the calendar server node and that in the directory server. unidssync
eliminates discrepancies, using the directory server as the authority. It should be run as part of a regular maintenance program.
Use the -galrefresh to refresh the Global Address List (GAL) which is used by the Oracle Connector for Outlook.
The calendar server must be up to run unidssync
.
Refresh the Global Address List (GAL).
<host>
Specify the host. Required if connecting to a remote host. To specify a port number use the following format for the hostname parameter: "hostname:port".
<node-ID>
Specify the node. Required if more than one node exists.
<sysOpPsw>
Provide the SYSOP password. If it is not provided on the command line, prompting for it occurs.
Synchronize the remote records also. By default, only records of local users, resources and event calendars are synchronized. This feature can be used in rare cases where a CWS replication request is lost or can't be serviced, resulting in un-synchronized remote records. Performing a synchronization with -remote will force a synchronization of remote records.
<user>
Used to specify a user, resource or event calendar to synchronize. See FORMAT OF THE <user> ARGUMENT for details on the <user> argument.
Print the current version number of unidssync
.
Print a usage message explaining how to run unidssync
.
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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note: If the ID key-value pair is specified for specifying a user in the <user> argument, all other key-value pairs specified along with it are ignored. |
Key | X.400 Field |
---|---|
N |
Event calendar name |
Key | X.400 Field |
---|---|
|
Resource name |
|
Resource number |
|
Resource unique identifier |
% unidssync -n 10 -host fergus
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 values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unidsup
- Report the status of the directory server.
unidsup [-q] [-host <hostname>] unidsup -v unidsup -h
unidsup
reports whether or not the directory server is running.
The calendar server must be up to run unidsup
.
<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".
Operate in quiet mode (produces no output when the directory server is up).
Print the version number of unidsup
.
Print a usage message explaining how to run unidsup
.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniencrypt
- Encrypt a password for inclusion in a calendar server configuration file.
uniencrypt -m <encryption_method> -s <string> uniencrypt -v uniencrypt -h
uniencrypt
uses the encryption method specified by the -m option to encrypt the string (usually a password) specified by the -s option. Any password supplied in a calendar server configuration file (such as those specified by the [LDAP]
bindpwd
and writednpassword
parameters) must first be encrypted using this utility.
uniencrypt
returns the encrypted password preceded by the encryption method used to generate it. For example, {std}ruyr84jf
. Generally, this entire value, including the encryption method and curly braces, should be enclosed in double quotes and included as the value of the password specified in the calendar server configuration file. For example:
[LDAP] bindpwd = "{std}ruyr84jf"
uniencrypt
can be run when the calendar server is up or down.
<encryption_method>
Specifies the encryption method to use. Accepted values currently include only std
, a proprietary affine cipher encryption method, and base64
. If this argument is not used, std
will be used by default.
<string>
Specifies the string to encrypt. If this is option is not used, uniencrypt
will prompt for the string to encrypt.
Print the current version number of uniencrypt
.
Print a usage message explaining how to run uniencrypt
.
% uniencrypt -s secure123 {std}q1qn1z0ij75
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unigroup
- Manage public and administrative groups.
unigroup -info [-host <hostname>] [-n <node-ID>] [[-p <psw>] [-uid <uid>] | [-krb]] unigroup -ls [<group>] [-members] [-host <hostname>] [-n <node-ID>] [[-p <psw>] [-uid <uid>] | [-krb]] unigroup -add <group> [-host <host>] [-n <nodeid>] [[-uid <uid>] [-p <password>] | [-krb]] unigroup -del <group> [-y] [-host <host>] [-n <nodeid>] [[-uid <uid>] [-p <password>] | [-krb]] unigroup -mod <group> -m <modifier> [-host <host>] [-n <nodeid>] [[-uid <uid>] [-p <password>] | [-krb]] unigroup -attach <group> -u <user> [-host <host>] [-n <nodeid>] [[-uid <uid>] [-p <password>] | [-krb]] unigroup -detach <group> -u <user> [-host <host>] [-n <nodeid>] [[-uid <uid>] [-p <password>] | [-krb]] unigroup -v unigroup -h
Unigroup
lets you manage public and administrative groups. You can create, modify and delete groups. You can list existing groups and their members.
Note that only administrative groups can be created.
Note that if a directory server is used, any groups created in the directory server are also included in the output of unigroup
. If members are listed, only the members of the directory server group who are also calendar users are output.
unigroup
can only be run if the calendar server is up.
<group>
Create an administrative group. See FORMAT OF THE <group> ARGUMENT for details on the <group> argument.
<group>
Add a user or resource to the specified group. See FORMAT OF THE <group> ARGUMENT for details on the <group> argument. Use -u to specify the user or resource to be added.
<group>
Delete the specified group. See FORMAT OF THE <group> ARGUMENT for details on the <group> argument.
<group>
Remove a user or resource from the specified group. See FORMAT OF THE <group> ARGUMENT for details on the <group> argument. Use -u to specify the user or resource to be removed.
<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".
Display information on the valid parameters for defining groups.
Use automatic Kerberos login. This option cannot be used with the -p and -uid options.
<group>
List the groups matching the specified group filter <group>. See FORMAT OF THE <group> ARGUMENT for details on the <group> argument. If no <group> argument is passed, all groups will be listed. Unless "node-id=*
" is used for the <group> argument, only the groups created on the local node (specified by the -n option) will be listed.
<modifier>
Specify the modification to be applied to a group using the <modifier> argument. This option is used with the -mod option. Use the same format as the <group> argument used with the -mod option. See FORMAT OF THE <group> ARGUMENT for details on the <modifier> argument.
Print the individual members of each group output. Use this option with the -ls option.
<group>
Modify a group's name or change it from public to administrative. You cannot change an admin group to public. Specify the group to be modified using the <group> parameter. See FORMAT OF THE <group> ARGUMENT for details on the <group> argument. Use -m to specify the changes to make.
<node-ID>
Specify the node on which the group is located. Required if more than one node is configured.
<password>
Provide the administrator's password; required if one is set. If this option is not used and a password is required, the user is prompted for it.
<user>
Used with the -attach and -detach options to specify a user or resource. See FORMAT OF THE <user> ARGUMENT for details on the <user> argument.
<user-ID>
The administrator's user ID. If none is specified the SysOp is used.
Used with the -del option to auto-confirm the deletion(s).
Print the current version number of unigroup
.
Print a usage message explaining how to run unigroup
.
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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note: If the ID key-value pair is specified for specifying a user in the <user> argument, all other key-value pairs specified along with it are ignored. |
Key | X.400 Field |
---|---|
|
Resource name |
|
Resource number |
|
Resource unique identifier |
The group 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 a 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. "NAME=Marketing/TYPE=Admin"
.
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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Key | X.400 Field |
---|---|
|
Group name |
|
Group type: |
ID |
Group ID number |
NODE-ID |
Group's node ID |
% unigroup -add "NAME=Marketing" -n 8 -p sesame unigroup: NAME=Marketing/ID=4096/NODE-ID=8/TYPE=Admin
% unigroup -attach "NAME=Marketing/TYPE=Admin" -u "S=Moore" -n 8 unigroup: Item has been attached to the group
% unigroup -ls "NAME=Marketing" -members -n 8 unigroup: NAME=Marketing/ID=4096/NODE-ID=8/TYPE=Admin Total Member(s): 1 User: S=Moore/G=Roger/UID=Rogerm/ID=260/Node-ID=8
% unigroup -ls "Node-id=*" -host jupiter -n 20
% unigroup -ls "NAME=Managers" -members -n 10
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniical
- Import, export, process or delete calendar entries to or from a user's agenda using iCAL objects.
uniical -import -u <user> [-f <filename>] [-charset <charset>] [-organizer <email>][ [-neverresolvemail] | [-alwaysresolvemail] ] -host <hostname> -n <node-ID> [[-uid <uid>][-p <password>] | [-krb]] uniical -process -u <user> [-f <filename>] [-charset <charset>] [-organizer <email>][ [-neverresolvemail] | [-alwaysresolvemail] ] -host <hostname> -n <node-ID> [[-uid <uid>][-p <password>] | [-krb]] uniical -export -u <user> [-f <filename>] [ [-end <date>] [-start <date>] | [-eventuid <uid>] ] -host <hostname> -n <node-ID> [[-uid <uid>][-p <password>] | [-krb]] uniical -del -u <user> [-f <filename>] [-charset <charset>] -host <hostname> -n <node-ID> [[-uid <uid>][-p <password>] | [-krb]] uniical -v uniical -h
The uniical
utility is used with the -import option to update a calendar user's agenda with information from an input file containing one or more iCAL VEVENT objects. The -del option is used to delete entries from the user's agenda. The -process option is used to process iCAL methods contained in the input file. This option can be used to create, modify and delete calendar entries using the same input file. Oracle iCALmethods are used to specify the operation to be applied on the particular event.
Each of the iCAL VEVENT objects describes either a new meeting or an existing meeting to be modified. By default, the name of the input file is icalin.ics
or icalin.txt
. See FORMAT OF THE INPUT FILE for more information on the input file.
When uniical
adds a new meeting to a user's agenda, it creates a UID for that meeting and maps the iCAL VEVENT attributes to calendar server attributes as described in the FORMAT OF THE INPUT FILE. By default, uniical
assumes that you intend to modify all existing meetings specified in the input file. If you specify the -del option, uniical
deletes all of these existing meetings from the user's agenda. See FORMAT OF THE INPUT FILE for more information on the minimal VEVENT attributes required to add, modify or delete events.
By default, to update a user's agenda, uniical
signs on to the specified calendar server node as the SYSOP. To sign-on as a designate user use the -uid and -p option to specify a designate user and his password.
When you export a user's agenda with uniical, both meetings that he organized and the meetings where he is only an attendee are exported. When an event is imported with uniical into a user's agenda, the event may be organized by the user (it's his meeting) or by someone else (he is only an attendee to that meeting). The event may also have other attendees beside the user.
Uniical
by default passes the -alwaysresolveemail
option to the server, so whether the user organizes the meeting or is simply an attendee, the other attendees are shown as internal.
An internal attendee is a user who also has a calendar account in the same calendar network. When a meeting is added with an internal attendee, a meeting will appear in that attendee's own agenda. The attendee's e-mail in the iCAL object is used to try to match the attendee to an existing calendar user. An external attendee is someone who is only listed as an attendee with no connection to the calendar network. Use the -neverresolvemail and -alwaysresolvemail options to change this behaviour by either forcing to match to internal users or to set every attendee as external attendees.
Use the -organizer option to override the organizer e-mail in the iCAL object.
uniical
outputs the UID attribute for each meeting it creates, modifies or deletes. It also logs any errors, along with the rest of its activity, in the $ORACLE_HOME/ocal/log/uniical.log
file.
uniical
runs on any machine running a calendar server. The calendar server must be up to run uniical
.
Note: This utility works properly only if the |
Always match the iCAL attendee email address to an existing calendar user when possible. With this option, the match will be attempted even when the organizer is someone else.
<charset>
Define the character set of the data in the input file. Valid values for <charset> include:
English:
Brazilian Portuguese, French, German, Italian:
Japanese:
Korean:
Simplified Chinese:
Traditional Chinese:
Delete from the user's agenda all existing events specified in the input file.
<date>
Specify the end date of the range of calendar data to be processed. Use the following date format: mm/dd/yyyy
<eventuid>
Specifies the event UID of the event to export.
Export all existing events in the range specified by the -end and -start options from the user's agenda to the output file. To export one specific entry from the agenda, use the -eventuid option to specify the single entry.
<filename>
Specify the name of the input file containing the iCAL VEVENT objects. By default icalin.ics
. For input, if icalin.ics
is not found, icalin.txt
is used. For output, icalin.ics
is the default file name used.
<hostname>
Specify the host name of the specified user's node database.
Import all existing events specified in the input file into the user's agenda.
Use automatic Kerberos login. This option cannot be used with the -p and -uid options.
<node-ID>
Specify the user's node. Required if more than one node exists on the specified host.
Never match the iCAL attendee email address to an existing calandar user. All iCAL attendees will be considered 'external attendees'.
<e-mail>
Specify the e-mail address of the event organizer which will override the one in the iCAL object.
<password>
Specify the password of the SYSOP or of the user specified by -uid. If this option is not used, prompting for the password occurs.
Process all existing iCAL methods specified in the input file. Each iCAL object in the input file must contain a METHOD
. Supported methods are the following:
X-ORACLE-IMPORT
The iCAL event will be created if it does not exist in the agenda, otherwise it will be modified
X-ORACLE-CREATE
The iCAL event must not exist in the agenda
X-ORACLE-MODIFY
The iCAL event must exist in the agenda
X-ORACLE-DELETE
Example of iCAL entry:
METHOD: X-ORACLE-MODIFY
<date>
Specify the start date of the range of calendar data to be processed. Use the following date format: mm/dd/yyyy
<user>
Specify the user, resource or event calendar in whose agenda to create, modify and delete events. See FORMAT OF THE user ARGUMENT for details on the <user> argument.
<user-ID>
The designate user's user-ID. If none is specified the SysOp is used. Specify the UID of a designate user for the user specified by the -u option.
Print the current version number of uniical
.
Print a usage message explaining how to run uniical
.
The input file contains one or more iCAL VEVENT objects, where each object has the following format:
BEGIN:VCALENDAR VERSION:2.0 PRODID:Oracle/Oracle Calendar Server 9.0.4 BEGIN:VEVENT <VEVENT attributes> END:VEVENT END:VCALENDAR
The <VEVENT attributes> are some or all of the attributes listed. Also listed is how uniical
maps these attributes to calendar server data fields.
DTSTART
Maps to start time. Specified in UTC (Universal Time Code). For example, "20020714T173000Z" represents July 15, 2002, at 5:30 PM. Note that the calendar server measures time in minutes, and discards the seconds value of this attribute.
DTEND
Maps to end time. Specified in UTC. See DTSTART
for detail.
DURATION
Maps to duration. Specified in the format P0DT
<hours>H
<minutes>M
<seconds>S
. For example, PT2H30M0S
specifies a duration of two and a half hours. The value of this attribute cannot exceed 23 hours and 59 minutes. Note that the calendar server measures time in minutes, and discards the seconds value of this attribute.
SUMMARY
Maps to event title. Limited to 64 characters.
PRIORITY
Maps to importance level. iCAL priorities 1, 3, 5, 7 and 9 map to importance levels highest, high, normal, low and lowest respectively. uniical
assigns a priority level of 5 (normal) if none is specified.
CLASS
Maps to access level. Case-insensitive. iCAL classes "public", "private" and "confidential" map to access levels "public", "personal" and "confidential" respectively. uniical
assigns the class "public" if none is specified.
LOCATION
Maps to location. Limited to 32 characters.
DESCRIPTION
Maps to details. Truncated if greater than 32 KB.
UID
Does not map directly to any calendar server field. The calendar server stores iCAL UIDs separately.
COMMENT
Discarded.
Commas in the values of the DESCRIPTION
, LOCATION
, SUMMARY
and COMMENT
attributes must be preceded with a backslash (\).
The minimal information required to create a new event is DTSTART
along with either DTEND
or DURATION
.
The minimal information required to modify an existing meeting is the correct UID
and start time of the meeting. uniical
first looks for the specified start time in the iCAL RECURRENCE-ID
attribute. If it does not find the value there, it uses the value of DTSTART
. To modify the start time of a meeting, you must specify the original start time in the RECURRENCE-ID
attribute, and the new start time in the DTSTART
attribute.
The minimal information required to delete an existing meeting is the correct UID
. This is also the only attribute uniical
takes into account for deletions. Thus, if two events have the same UID
, there is no way to use uniical
to delete only one of them.
uniical
creates repeating meetings if two or more new iCAL events have the same UID
but different DTSTART
values. However, if one of these events is later input for deletion, uniical
deletes all instances of the recurring meeting.
If a new event appears twice in the input file, and the second instance does not have its own unique UID
, the second event overwrites the first.
The following input file contains two iCAL VEVENT objects. The first describes a new meeting to be created in the specified user's agenda at 4:00 PM on January 31, 2001; the second describes a modification to be made to an existing meeting. The modification to the existing meeting changes the start time from 4:30 PM to 4:45 PM. uniical
uses the UID
and the start time specified by the RECURRENCE-ID
attribute to find the meeting in the specified user's agenda. It also updates the meeting information with the changes specified by other attributes.
BEGIN:VCALENDAR VERSION:2.0 PRODID:Oracle/Oracle Calendar Server 9.0.4 BEGIN:VEVENT DESCRIPTION: NYPMRN: 99999990DXMRN:9999999990DX Comment: <appointment comments> LOCATION: Type: <type> IDX# <IDX visit identifier> DTSTART:20010131T160000Z DURATION:P0DT0H20M0S COMMENT:IDX visit identifier SUMMARY:Carter Dickson PRIORITY:3 END:VEVENT END:VCALENDAR BEGIN:VCALENDAR VERSION:2.0 PRODID:Oracle/Oracle Calendar Server 9.0.4 BEGIN:VEVENT DESCRIPTION: NYPMRN: 99999990DXMRN:9999999990DX Comment: <appointment comments> LOCATION: Type: <type> IDX# <IDX visit identifier> DURATION:P0DT0H20M0S SUMMARY:John Dickson Carr COMMENT:IDX visit identifier DTSTART:20000215T164500Z RECURRENCE-ID:20000215T163000Z PRIORITY:6 END:VEVENT END:VCALENDAR
The <user> argument, which is used to represent a user, resource or event calendar, 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. For all keys except the ID key, 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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
The format parameters listed in the third column are used with the -format option to configure the presentation of a listing (see EXAMPLES). For a more complete list of the keys and formats that can be used, use the -info option.
Key | X.400 Field | Format Parameter |
---|---|---|
N |
Event calendar name |
%N% |
Key | X.400 Field | Format Parameter |
---|---|---|
|
Resource name |
%R% |
|
Resource number |
%N% |
|
Resource unique identifier |
|
/pediatric/IDXtoCST.txt
. Use the designate user Alfred Kelvin to perform the update to Mark Johnson's agenda:
% uniical -import -u "S=Johnson/OU1=Pediatrics" -uid "UID=akelvin" -p PSWforKelvin -host horus -n 12 -f /pediatric/IDXtoCST.txt uniical: Event has been imported. UID = 20030614T160536Z-423-18b6-Oracle@server1 uniical: Event has been imported. UID = 20030614T150536Z-234-18b6-Oracle@server1 uniical: Event has been imported. UID = 20030614T160566Z-432-18b6-Oracle@server1 uniical: Event has been imported. UID = 20030614T160586Z-243-18b6-Oracle@server1
MJohnson.txt
:
% uniical -import -u "S=Johnson/OU1=Pediatrics" -p SysOpPsw -host horus -n 12 -f /pediatric/IDXtoCST.txt > MJohnson.txt
./axe.txt
from the agenda of user Mark Johnson in the organizational unit "Pediatrics" on node 12 of host horus:
% uniical -del -u "S=Johnson/UID=Pediatrics" -uid "Pediatrics" -p PSWforJohnson -host horus -n 12 -f ./axe.txt uniical: Event has been deleted. UID = 20030616T160546Z-403-18b6-Oracle@server1 uniical: Event has been deleted. UID = 20030616T167776Z-403-18b9-Oracle@server1
/users/unison/log/uniical.log
uniical
logs its activity in this file.
./icalin.txt
The default input file for uniical
.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
See IETF RFC 2445 for additional information on iCAL.
unil2bendian
- Convert a calendar server node database from a format for little-endian Windows NT processors to a format for big-endian processors. For more details on this utility, contact Oracle support.
unil2bendian [-n <node-ID>] unil2bendian -v unil2bendian -h
unil2bendian
is used when migrating a node database from a calendar server running on a little-endian Windows NT machine to one running on a big-endian UNIX machine (HP-UX, Solaris, or AIX).
This utility converts the *.dat
files of the node database from little-endian to big-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.
unib2lendian
is the complementary utility for converting files from big-endian UNIX format to little-endian Windows NT format.
unil2bendian
can only be run when the calendar server is down.
<node-ID>
Specify a node to convert. Required if more than one node exists on the local host.
Print the current version number of unil2bendian
Print a usage message explaining how to run unil2bendian
.
The following example converts node 45, and moves it from a calendar server running on a little-endian machine to a calendar server running on a big-endian system.
unil2bendian
on the target node.
unil2bendian -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.
$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.
*.dat
files in the perm_conv
directory to the $ORACLE_HOME/ocal/db/nodes/
<N#>/perm
directory on the big-endian system.$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.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
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 big-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.
Exit values are:
0 Success
1 Failed to convert the database
2 Usage error
unidbfix, unistart, unistop, uninode
unilogons
- Display calendar server SIGNON/SIGNOFF statistics.
unilogons [-s <starttime>] [-e <endtime>] [-i <interval>] [-f <filename>] unilogons -t -s <starttime> -e <endtime> -i <interval> [-f <filename>] unilogons -t [<time>] [-f <filename>] unilogons -v unilogons -h
unilogons
displays the signon and signoff activity of users on a calendar server at a specific time or during a specific time period. By default it uses the information in the $ORACLE_HOME/ocal/log/act.log
file. The -f option may be used to specify another input file.
Use the -t option to display activity at a given time and date. The -s and -e options can be used to display activity during a specified period of time. The -i option specifies a regular time interval (e.g. every 15 minutes) within the specified period.
By default, all activity between the default start-time (the first minute of the current day) and the default end-time (the current system time) is displayed.
The calendar server must be up to run unilogons
.
<endtime>
Specify an end time for the statistics. Without this option, the default end time is the current time of the current day. See FORMAT OF THE time ARGUMENTS for details on how to specify <endtime>.
<filename>
Specify the name of the input file. By default the input file is $ORACLE_HOME/ocal/log/act.log
. The input file specified with the -f option must be in the same format as the act.log
file.
<interval>
Specify a time interval. The default interval is <endtime> minus <starttime>. See FORMAT OF THE interval ARGUMENTS for details on how to specify interval.
<starttime>
Specify a start time for the statistics. Without this option, the default start time is the first minute of the current day. See FORMAT OF THE time ARGUMENTS for details on how to specify <starttime>.
[
<time>]
If used without the -s, e, and -i options, this displays statistics for the current time (-t) or for a given time (-t <time>). When used together with all of the -s, -e, and -i options, the -t (without a time argument) restricts output to activity at only the precise times determined by the interval (-i) argument. See the last two EXAMPLES for sample output of the -s, -e, -i options both with and without the -t option. See FORMAT OF THE time ARGUMENTS for details on how to specify time.
Print the current version number of unilogons
.
Print a usage message explaining how to run unilogons
.
The <starttime>, <endtime>, and <time> arguments may each be expressed as either:
where
day
is a number between 1 and 31
month
is either the full name of the month or the first three letters of the full name (e.g. jan, feb, mar, etc.) (month is case-insensitive)
year
must be 1991 or higher and must be specified using four digits
time
is in the form HH:MM or HH:MM:SS (HH is an integer between 0 and 23, MM is an integer between 0 and 59, and SS is an integer between 0 and 59)
The order of the individual elements in the argument is unimportant. What is important is that either day and month be specified, or time be specified. For example, the following are all valid:
Feb 22 2003 10:00:00 22 february 10:00:00 10:00:00 february 22 2003 2003 feb 22 feb 22 10:00:00
Default values for day, month, year and time are current day, current month, current year and current system time respectively.
Any missing field in time (HH, MM, or SS) is replaced with the current HH, MM, or SS value. Thus, if the current date and time is March 12 2003 10:12:34, and only HH:MM are specified in the argument, the SS becomes "34":
-e 12:41 -> March 12 2003 12:41:34 -s 12:41 -> March 12 2003 12:41:34
If none of the time fields are specified, starttime defaults to the first minute of the day, and endtime defaults to the last minute of the day:
-s feb 22 -> feb 22 2003 00:00:00 -e feb 22 -> feb 22 2003 23:59:59
The interval argument must be an integer greater than zero and be input as minute, hour or day as follows:
minutes: 1m, 2m, etc. up to 999999999m (9 digits) hours: 1h, 2h, etc. up to 9999999h (7 digits) days: 1d, 2d, etc. up to 99999d (5 digits)
unilogons -t
unilogons -t oct 6 2003 15:00
This would produce the following output:
Time 1: Oct 6 2003 15:00:00 ------------------------------------- Client Logged-On Name & Version unisncd 2 Windows/32/Oracle Calendar 1 ------------------------------------- Totals: 3
unilogons -t -s oct 6 2003 15:00:00 -e oct 6 2003 17:00:00 -i 15m
A sample section of the output from this command shows the form of what is output for each of the times 15:00:00, 15:15:00, 15:30:00, etc., up to 17:00:00. (Compare this with the output of the next example, where the -t is removed from the command line.)
Time 1: Oct 6 2003 15:00:00 ------------------------------------- Client Logged-On Name & Version unisncd 2 Windows/32/Oracle Calendar 1 ------------------------------------- Totals 3
unilogons -s oct 6 2003 15:00:00 -e oct 6 2003 17:00:00 -i 15m
For each of the 15-minute time intervals within the entire time period, output similar to the following is displayed:
Time Period 1: From Oct 6 2003 15:00:00 Till Oct 6 2003 15:15:00 -------------------------------------------------------------------------------- Client Logons Logoffs Average Time Median Time Name & Version Logged-On(hrs) Logged-On(hrs) Not Available 0 2 20.71 23.98 unisncd 2 0 9.83 9.83 Windows/32/OracleCalendar 4 4 0.02 0.02 -------------------------------------------------------------------------------- Totals 6 6
$ORACLE_HOME/ocal/log/act.log
By default unilogons
obtains its information from this file. Note that this file is only created if the [ENG] activity
parameter in unison.ini
is set to "TRUE
".
unilogons
may take some time to finish depending on the size of the input file.
The disk space requirement to run unilogons
is one and a half times the input file. Thus, if the size of the input file is 8 Mb, approximately 12 Mb of free disk space is required to run unilogons
. unilogons
creates its temporary files in the $ORACLE_HOME/ocal/tmp
directory so sufficient free space must exist in that directory.
Exit values are:
0 Success
1 Failure
unimmimpsrv
- A utility to import data from MeetingMaker servers into Oracle Calendar Server nodes.
unimmimpsrv unimmimpsrv -v unimmimpsrv -h
The unimmimpsrv
utility is used to migrate data from MeetingMaker servers to Oracle Calendar nodes. unimmimpsrv
consults the unimmimpsrv.ini
file to determine which MeetingMaker files to import, and which nodes receive the data. Note that unimmimpsrv
does not work with Oracle Calendar Servers using directory servers.
Be aware of the following before running unimmimpsrv
:
If only a subset of the MeetingMaker servers attached to a hub are imported, the following apply:
To migrate data from MeetingMaker to Oracle Calendar, execute the following steps:
*.dat
file.unimmimpsrv
utility to read the $ORACLE_HOME/ocal/misc/unimmimpsrv.ini
file and import the MeetingMaker *.dat
files into the specified Oracle Calendar node(s).uniuser
utility to apply the settings in the user.ini
file to the newly imported users or to otherwise modify the information associated with these users.Print the current version number of unimmimpsrv
.
Print a usage message explaining how to run unimmimpsrv
.
The following chart details the mapping between MeetingMaker and Oracle Calendar transferable data:
The following data is lost during the migration to Oracle Calendar. Note: "(read)" indicates the unimmimpsrv
utility supports the data but Oracle Calendar does not.
Lost Administrative Data
Lost User Data
Lost Resource Data
Lost MeetingMaker Activities, Banners & Meetings Data
Lost MeetingMaker Todos Data
$ORACLE_HOME/ocal/log/unimmimpsrv.log
This file records the start time, end time and duration as well as all importation steps and any errors.
$ORACLE_HOME/ocal/misc/unimmimpsrv.ini
This file contains the settings used for the importation process. See unimmimpsrv.ini
for details.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unimmimpsrv.ini, uniuser
unimvuser
- Move a user from one calendar server node to another.
unimvuser -u <user> -host1 <hostname1> -host2 <hostname2> -n1 <node-ID1> -n2 <node-ID2> [-p1 <sysOpPsw1>] [-p2 <sysOpPsw2>] [-up <userPsw>] [-UIDpreserve] [-verbose] unimvuser -v unimvuser -h
unimvuser
moves a user from one calendar server node to another. Designate and remote designate rights are preserved.
Note: See the WARNINGS section before attempting to move a user from a 5.0 or greater node to a 4.0 or earlier node. |
The move operation makes the following changes to the user information:
unimvuser
logs these changes, along with the rest of its activity, in the $ORACLE_HOME/ocal/log/unimvuser.log
file.
It is important to understand that the move operation may still be in progress even after unimvuser
has successfully completed. In particular, work is being done by the destination node (the node to which the user has moved) and by remote nodes (where other users reside who may have invited the user). Until the work is complete, the moved user sees an incomplete agenda.
The time required to complete the move operation depends on the number of requests waiting in the request queue of the Corporate-Wide Services daemon/service. For this reason, it is advisable to run unimvuser
during off-peak hours for the calendar server.
In addition, the user being moved should not attempt to sign in to the calendar server before unimvuser
has completed, nor should any other user attempt to work as a designate for the user being moved. Any changes made under these circumstances will be lost.
Never run more than one unimvuser
operation at the same time. Even if the users involved are on different nodes and you run unimvuser
on different calendar server hosts, the users may share some meetings or events; this scenario can cause database corruptions.
unimvuser
can move a user from a node using an external directory server to a node using the calendar server's internal directory, but cannot move a user from a node using the calendar server's internal directory to a node using an external directory server.
Always use the most recent version of unimvuser
, even when moving a user between nodes on calendar server hosts of earlier versions. For example, if your node network has two calendar server hosts of version 5.4 and one host of version 9.0.4, you should use the unimvuser
utility in the bin
directory of the 9.0.4 server.
Be aware also that differences in the configurations between the source host and the destination host may cause problems or block the move entirely. For example, if the maximum number of instances of a recurring meeting (unison.ini
[ENG]
maxinstances
parameter) on the source server is set higher than on the destination server, and the user to be moved owns a recurring meeting with more instances than the destination host allows, the move will fail.
The calendar server must be up to run unimvuser
with all connected nodes enabled.
<hostname1>
Specify the host name of the source node. To specify a port number use the following format for the <hostname> parameter: "hostname:port".
<hostname2>
Specify the host name of the destination node. To specify a port number use the following format for the <hostname> parameter: "hostname:port".
<node-ID1>
Specify the source node.
<node-ID2>
Specify the destination node.
<sysOpPsw1>
Provide the SYSOP password for the source node. If this option is not used, prompting for the password occurs.
<sysOpPsw2>
Provide the SYSOP password for the destination node. If this option is not used, prompting for the password occurs.
<user>
Specify the user to be moved. See FORMAT OF THE user ARGUMENT for details on the proper specification of the user argument. For directory servers, the user must already exist in the directory server used by the destination node.
Preserve original Calendar SDK event UIDs. This option is required if the Calendar SDK is used on both the source and the destination node.
<userPsw>
To be used for internal directory only. Specifies a new password for the user. If this option is not used, the user will be able to log into the calendar server without a password. In the case of a directory server, this option has no effect since the password is stored in the directory server and thus remains unchanged.
Use verbose mode.
Print the current version number of unimvuser
.
Print a usage message explaining how to run unimvuser
.
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. For all keys except the ID key, 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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
% unimvuser -u "ID=354" -host1 horus -host2 nut -n1 12 -n2 25
% unimvuser -u "UID=smithjc" -host1 horus -host2 nut -n1 12 -n2 25
$ORACLE_HOME/ocal/log/unimvuser.log
unimvuser
logs its activity in this file.
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 values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniuser
uninode
- Administer a calendar server node network.
uninode -add [-nologinfo] -host <hostname> uninode -apply [-y | -n] [-nologinfo] [-p <SysOpPsw>] uninode -cws [-nologinfo] [-compact] [-n <node-ID> | -host <hostname> | -group <group>] uninode -edit [-e <editor>] [-p <SysOpPsw>] uninode -import [-nologinfo] [-p <SysOpPsw>] uninode -init [-nologinfo] [-p <SysOpPsw>] uninode -reset [-nologinfo] [-p <SysOpPsw>] [-n <node-ID> | -host <hostname> | -group <group>] uninode -retry [-nologinfo] [-p <SysOpPsw>] [-n <node-ID> | -host <hostname> | -group <group>] uninode -snc [-nologinfo] [-compact] [-n <node-ID> | -host <hostname> | -group <group>] uninode -test -n <node-ID> | -host <hostname> | -group <group> uninode -v uninode -h
uninode
is a centralized tool for setting up and administering a calendar server node network. See EXAMPLES for an example of setting up a node network. Use uninode
to add and remove nodes from the node network, as well as to add and remove connections between nodes. Also use uninode
to make queries about the node network configuration and about the status of remote connections.
uninode
uses the node network configuration information in the nodes.ini
file to configure the node network. Only one nodes.ini
file should exist for a node network, regardless of how many calendar servers are linked. Furthermore, you manage the calendar server node network, that is you run uninode
, from the machine on which this file exists. When your node network includes coexistence of multiple calendar server versions, always make sure that the host of the nodes.ini
file is of the most recent version.
The <sysOpPsw> is the SYSOP password for the node in the calendar server network with the lowest node-ID on the machine hosting the nodes.ini
file.
Use the -n, -host or -group to restrict uninode
's actions to certain nodes in the nodes.ini
file. -n <node-ID> restricts uninode
to the specified node, -host <hostname> to the nodes on the specified host, and -group <group> to the nodes in the specified grouping of nodes. <group> may be one of the following:
all
all included (+) and all excluded (-) nodes
included
all included (+) nodes
excluded
all excluded (-) nodes
<group> may also be a customized group name defined in nodes.ini
. Consult your Oracle Calendar Administrator's Guide for further details on the meaning of each of these values. If none of these values are specified, uninode
will assume the value all
.
If you are using a directory server, you may want to run unidssync
on each node before running uninode
to ensure that the local information in each node is synchronized with what is in the directory server. Note that all nodes in a calendar server node network must use the same directory server.
uninode
only runs if the calendar server is up.
<hostname>
Add all nodes found on the specified host to the nodes.ini
file. This option first determines which nodes exist on the specified host. It then removes all lines for that host in the nodes.ini
file, and finally adds a line for each node found on the host. Nodes are added as excluded nodes. You must edit the nodes.ini
file to include them in the network.
Apply the configuration in the nodes.ini
file.
uninode
first verifies that:
nodes.ini
file is correctuniengd
and unisncd
servers are upuniengd
is greater than A.01.15nodes.ini
file exists only on the host currently running uninode
If any of these verifications fails, uninode
terminates.
Otherwise, it proceeds to check the remote node information in each of the nodes involved, and if it finds there are entries missing, it prompts the user to confirm the addition of the missing entries. Use the -y or -n option to automatically provide a response. Note that uninode
does not delete any surplus entries from any of the nodes.
Truncate the host name if longer than 28 characters in order to output 80 character lines.
Print the following information for each connection between two nodes. This includes information from the CWS daemon/service.
The number of TCP/IP connections, between the two nodes, configured in the nodes.ini
file.
The actual number of TCP/IP connections between the two nodes.
The number of CWS requests currently in the CWS queue.
The number of CWS requests processed.
The number of items (users and resources) in the local copy of the remote directory.
<editor>
Safely edit a COPY of the nodes.ini
file using the specified text editor. uninode
first performs the verifications described in the -apply option and terminates if any of the verifications fails. If all verifications succeed, it invokes the editor. On exit from the editor uninode
parses the edited file, and, if it does not find any errors, updates the original nodes.ini
file. If uninode
finds errors in the edited file, it prompts the user to either re-edit the file or abort the operation.
<group>
Restrict the nodes to those of the group specified by <group>. <group> can be all
, included
or excluded
or a group name defined in nodes.ini
.
<hostname>
Restrict the nodes to those on the specified host.
Same as -apply with the -y option.
Construct a nodes.ini
file from the currently running node network configuration. The node with the lowest node-ID on the machine hosting the nodes.ini
file is the one from which uninode
begins construction of the file. If a nodes.ini
file already exists, uninode
prompts for confirmation to overwrite it.
When used with the -apply option, prevent any correction of node information inconsistency.
<node-ID>
Specify the node
Do not write to the log file. By default, uninode
logs any errors, as well as any output it sends to the screen, to the uninode.log
file.
<sysOpPsw>
Specify the SYSOP password. Without this option, prompting for the password occurs.
Reset the statistics of a Synchronous Network Connection (SNC) daemon. It is recommended that you reset all nodes at the same time by running uninode -reset all
. Resetting the statistics allows the administrator to compare the statistics for different nodes at a later time.
Restart the retry mechanism of an SNC daemon. When there are fewer connections available than are configured, the SNC daemon attempts to acquire new connections at specific time intervals. It retries at intervals of 1, 2, 4, 8, 16, 32, and finally every 64 minutes. This option resets the interval to 1 minute. One use of this option might be to run uninode -retry
all
after a network-related problem is solved.
Print the following information on the TCP/IP connections for the specified node, or for each node in the specified group or on the specified host.
The number of TCP/IP connections to the node configured, as per the information in the nodes.ini
file.
The actual number of TCP/IP connections to the node.
The number of connections to the node currently available.
The number of connections to the node currently in use.
The number of times the SNC daemon lost a connection to the node.
The time (expressed in the format <mm>:<ss> format) before the next attempt to reconnect a lost connection.
The number of requests currently in the queue.
The number of cancelled requests.
The number of checks for queued requests. Checks are performed when a connection is waiting in the queue.
The number of requests for connections the SNC daemon/service granted since it started.
Verify that it is possible to connect to a node or group of nodes. See the -apply option for a list of the items uninode -test
verifies.
Auto-confirm the correction of any node information inconsistency when you use the -apply option.
Print the current version number of uninode
.
Print a usage message explaining how to run uninode
.
You have a company with offices in three different countries. Each office runs its own calendar server. You want to set up a node network and manage it from the calendar server running on "gravlax" in Sweden.
nodes.ini
file.
% uninode -init
Since no node network currently exists, uninode
creates an empty nodes.ini
file with sample lines included as comments.
% uninode -add gravlax % uninode -add gnocchi % uninode -add biryani
nodes.ini
file.
% cat nodes.ini - H=biryani/N=32 - H=biryani/N=31 - H=gnocchi/N=25 - H=gnocchi/N=24 - H=gnocchi/N=23 - H=gnocchi/N=22 - H=gnocchi/N=21 - H=gravlax/N=13 - H=gravlax/N=12 - H=gravlax/N=11
% vi $ORACLE_HOME/ocal/misc/nodes.ini
The nodes.ini
file now contains the following lines.
% cat $ORACLE_HOME/ocal/misc/nodes.ini + H=biryani/N=32/ALIAS=salesIndia/GR=india + H=biryani/N=31/ALIAS=adminIndia/GR=india - H=gnocchi/N=26/ALIAS=tempItaly/GR=italy + H=gnocchi/N=25/ALIAS=supportItaly/GR=italy + H=gnocchi/N=24/ALIAS=financeItaly/GR=italy + H=gnocchi/N=23/ALIAS=r&dItaly/GR=italy + H=gnocchi/N=22/ALIAS=salesItaly/GR=italy + H=gnocchi/N=21/ALIAS=adminItaly/GR=italy - H=gravlax/N=16/ALIAS=tempSweden/GR=sweden + H=gravlax/N=13/ALIAS=r&dSweden/GR=sweden + H=gravlax/N=12/ALIAS=salesSweden/GR=sweden + H=gravlax/N=11/ALIAS=adminSweden/GR=sweden included:2 india:+2 italy:+3 sweden:+2
The node network has the following characteristics:
In this configuration, the total number of connections from node 13 is 22 (two to each of the other nine nodes in the network gives 18, plus two to each of the other two included nodes in the "sweden" group gives 4).
Consult your calendar server's Administrator's Guide for rules on configuring connections between nodes.
Next, apply the configuration. Since this is the first time that nodes "see" other nodes, you expect inconsistencies in their remote node directories. For this reason you use the -y option.
% uninode -apply -y
During execution of this command, uninode
prints out information on the work it is performing. For example:
Processing node 11 connected to gravlax, node 11 connected to gravlax, node 12 added 11->12, TCP/IP connection placed a request in the CWS queue to get node 12 user directory
$ORACLE_HOME/ocal/misc/nodes.ini
Contains the list of nodes and the rules that describe the calendar server's node network configuration.
$ORACLE_HOME/ocal/log/uninode.log
By default, uninode
logs any errors, as well as any output it sends to the screen, to this file.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unioidconf
- Configure the Oracle Internet Directory for calendar. This utility is used by the installation process of the calendar server.
unioidconf -setup <SysOpPsw> -D <binddn> [-w <bindPsw>][-f <filename>] unioidconf -grantproxyprivilege <dn> [-f <filename>] [[-D <bindDN>][-w <bindPsw>] | [-p <SysOpPsw>]] unioidconf -listproxyprivilege [-f <filename>] [[-D <bindDN>][-w <bindPsw>] | [-p <SysOpPsw>]] unioidconf -revokeproxyprivilege <dn> [-f <filename>] [[-D <bindDN>] [-w <bindPsw>] | [-p <SysOpPsw>]] unioidconf -v unioidconf -h
unioidconf is used by the installation process to configure the Oracle Internet Directory for the Calendar application.
The -grantproxyprivilege and -revokeproxyprivilege keywords are used to grant or revoke proxy privilege to a user. The proxy privileges can be listed using -listproxyprivilege.
The -setup flag is used to configure OiD for calendar.
<bindDN>
Specified the binding DN.
<filename>
Specify the calendar configuration file. By default, the file $ORACLE_HOME/ocal/misc/unison.ini
is used.
<dn>
Grant proxy privilege to user specified by <dn>.
List the proxy privilege.
<SysopPsw>
Provide the current administrator password.
<dn>
Revoke proxy privileges from user specified by <dn>.
<bindPsw>
Specified the binding DN password.
Print the current version number of unioidconf
.
Print a usage message explaining how to run unioidconf
.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Grant proxy privilege to John Doe:
% unioidconf -grantproxyprivilege "cn=John Doe,cn=users, dc=oracle,dc=com" -D cn=orcladmin -w welcome
or:
% unioidconf -grantproxyprivilege "cn=John Doe,cn=users, dc=oracle,dc=com" -p adminpassword1
unipasswd
- Change a user's password or the calendar server SYSOP password.
unipasswd [-u <user> | -sysop] [-n <node-ID>] [-host <hostname>] [-p <password>] unipasswd -v unipasswd -h
unipasswd
changes the password of the SYSOP of a given node. unipasswd
can also be used to change a user's password.
In an Oracle Internet Directory installation, after changing the SYSOP password via a node, the SYSOP password on all the other nodes of the same server will also be changed.
Note that the -sysop and -u options are mutually exclusive. unipasswd
cannot be used to change a resource or an event calendar's password. But this can be done using uniuser
.
unipasswd
only runs if the calendar server is up.
<user>
Change a user's password. Use the <user> argument to specify which user. See FORMAT OF THE <user> ARGUMENT for details on how to specify a user.
<hostname>
Specify the host on which the operation is to be performed. The default is the local host. To specify a port number use the following format for the <hostname> parameter: "hostname:port".
<node-ID>
Specify the node on which the password is to be changed. Required if more than one node exists.
<password>
Provide the current administrator password. Required if -u option is used and a SYSOP password is set. If this is required and it is not supplied on the command line, prompting for it occurs.
Change the password of the SYSOP.
Print the current version number of unipasswd
.
Print a usage message explaining how to run unipasswd
.
The entry 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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
% unipasswd -host jupiter -n 20
% unipasswd -u "S=Leblanc/G=Jean" -n 10
This utility uses the [ENG]allowpasswordchange_user
parameter in unison.ini
to determine whether or not it can modify a user password. If this value is set to "FALSE
", then the user password cannot be modified by this utility. The parameter [ENG]allowpasswordchange_reserved [sysop]
is used to determine whether or not it can modify the SysOp password.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniping
- Ping another calendar server.
uniping [-host <hostname>] [-n <node-ID>] [-u <user>] [-p <password>] [-i <numsec>] [-allnodes] [-s <size>] [-stats] [-log] [-time] uniping -v uniping -h
uniping
sends echo messages to a node or a node network. Receiving nodes reply to the message, and uniping
prints the elapsed time between sending the original message and receiving the replies. Use this utility to verify that a node is up, or to measure server response time under various load conditions.
Before sending any messages, uniping
first authenticates the specified user on the specified node. uniping
only sends messages if this authentication is successful.
uniping
runs whether the calendar server is up or down.
Send the echo message to all nodes connected to the node network containing the specified node.
<hostname>
Specify the name of a calendar server host. To specify a port number use the following format for the hostname parameter: "hostname:port".
<numsec>
Repeat the echo message with intervals in seconds specified by <numsec>. If this option is not used, uniping
sends only one echo message to each specified node.
Print errors to a log file ($ORACLE_HOME/ocal/log/uniping.log)
.
<node-ID>
Specify a node to connect to. Required if more than one node exists on the calendar server specified by the -host option.
<password>
Provide the SYSOP password or the password for the user specified by the -u option. If you do not use the -p option, uniping
will prompt you for the password.
<size>
Specify the size of the echo message in bytes. The default is 64 bytes.
Display statistics on startup.
Display the time at which each message is sent.
<user>
Specify a user name to use for authentication. If this option is not used, SYSOP is used by default. See FORMAT OF THE <user> ARGUMENT for details on how to specify a user.
Print the version number of uniping
.
Print a usage message explaining how to run uniping
.
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. For all keys except the ID key, 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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
% uniping -host scribe -n 14 Enter password: scribe,14: 40 ms.
% uniping -n 60 -u "S=Hammett/G=Dashiell" -allnodes -time Enter password: Fri Jul 07 10:23:41 2000: scribe,14: 40 ms. Fri Jul 07 10:23:41 2000: scribe,60: 0 ms. Fri Jul 07 10:23:41 2000: scribe,66: 114 ms.
Exit values are:
0 Success
1 Failure
2 Usage error
unireqdump
- View, and optionally delete, requests in the queue of the Corporate-Wide Services (CWS) daemon.
unireqdump [-delete] [-excl <filter>] [-incl <filter>] [-u <itemnum>] [-rn <node-ID>] [-y] [-reqid <ID>] [-reqtype <code>] [-reqgroup ID] [-n <node-ID>] [-p <sysOpPsw>] [nolist] [-nototal] unireqdump -v unireqdump -h
unireqdump
outputs the set of requests currently in the queue of the Corporate-Wide Services daemon/service, unicwsd
. The utility is also used to delete requests from the queue (using the -delete option).
By default, all requests in the queue are output. The -excl, -incl, -u, -rn, -reqid, and -reqtype options allow you to select requests satisfying specific criteria. These options are applied successively so each of the requests in the output must meet the combined criteria for all of the options specified. Use -reqid if you want to select a specific request from the queue.
Numeric arguments can be either decimal or hexadecimal values (where hexadecimal values are prefixed by "0x
"). The single exception is the ID argument to the -reqid option, where a hexadecimal value is always assumed, even if the "0x
" prefix is not present.
unireqdump
can only be run if the calendar server is up.
Delete from the queue the requests that match the filters. After each request is output, the user is prompted to confirm whether or not they wish to delete it. The -y option may be used along with this option to tell unireqdump
to automatically delete ALL of the requests in the output, without prompting for confirmation.
<filter>
Set an exclusion filter. Requests matching this filter are excluded from the output. The possible filters are:
<filter>
Set an inclusion filter. Requests matching this filter are included in the output. The possible filters are listed under the -excl option.
<node-ID>
Specify a node to connect to. Also used to select the requests which originated from this node. Required if more than one node exists on the server running unireqdump
.
Do not list the requests that are in the queue.
Do not display the summary (totals at the end of the output).
<sysOpPsw>
Provide the SYSOP password of the node specified by the -n option. If the password is not supplied on the command line, prompting for it occurs.
<itemnum>
Select only requests matching the specified calendar account (user, resource or event calendar) number. itemnum
is the numeric ID of the user, resource or event calendar.
Used with the -delete option to tell unireqdump
to automatically delete all of the requests in the output, without prompting for confirmation. Use this option with care!
<node-ID>
Select only requests destined for the specified remote node.
<group>
Select the request of the group specified by <goup>. Valid values for <group> are: "replication", "SMS" or "mail".
<ID>
Select the request with the specified ID. ID is a hexadecimal value (it is not necessary to prefix the value with "0x", though doing so causes no harm).
<code>
Select the request of type <code>. The type can be expressed numerically by its transaction code (the numeric values are available in the documentation for the calendar programming interface), or as one of the following strings:
agendaget attendadd echo eventattend eventcreated eventdeleted eventmodified foreignerdeleted instanceadded instancemodified itemdeleted itemmodified mailmessagepost nodeitemsget notifynewevent notifynewinstance securityadd securitydeleted securitymodified These strings also appear in the output in the "TrCode" field for each request listed.
Print the current version number of unireqdump
.
Print a usage message explaining how to run unireqdump
.
unireqdump -n 10 -p sysOpPsw
unireqdump -delete -n 10 -p sysOpPsw
unireqdump -excl serviced -p sysOpPsw
unireqdump -delete -excl serviced -remotenode 20 -reqtype eventattend -n 10 -p sysOpPsw
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unirestore
- Restore a user's agenda from a backup.
unirestore -u <uid> -path <bkpPath> [-futureReplies] [-noAddAttendee] [-logAll] -n <node-ID> [-host <hostname>] [-p <sysOpPsw>] unirestore -ls <user> -path <bkpPath> -n <node-ID> [-host <hostname>] [-p <sysOpPsw>] unirestore -v unirestore -h
unirestore
restores a user's calendar data from a backup file. A user calendar account can be restored even if it has been deleted completely, in which case a calendar account is created for the user. If there is a directory server, the user must be in the directory.
The -u option is used to specify the UID of the user you wish to restore. The -path option indicates the path to the backup files. This is the path to the directory which includes a db
directory. For example: "-path /backups/cserver/jan0799
".
The -ls option to list users contained in a backup. The <user> argument restricts unirestore
to list only the users that match the <user> filter. See FORMAT OF THE <user> ARGUMENT for details on how to specify <user>.
By default, for agenda entries scheduled in the future and created by other users, any changes the user has made to his attendance status are not restored. For meetings that the user does own, the attendance status of all attendees are reset to "to be confirmed" as if the meetings were newly created.
Use the -futureReplies option if you want to force the restoration of the users' replies to invitations from the backup. With this option, any changes the user has made to his attendance status (accepted, refused, etc.) for agenda entries in the future (after the restoration date) which were created by others will be restored. Also, for meetings that the user created, the attendees' attendance status will be restored from the backup.
By default, if the user was invited to a meeting in the backup and he is no longer invited to that meeting in the current database (this can happen if for example, the user was accidently deleted from the database), he will be added back as an attendee. But in cases where for example the meeting organizer deleted the user from the attendee list after the backup was made, you may want to use the -noAddAttendee option to avoid re-adding the user to the attendee list of meetings that other users created and own and intentionally removed the user.
unirestore
only runs if the calendar server is up. There is no need to restart the server after running unirestore
.
Restore the user's attendance status for future agenda entries.
<hostname>
Specify the host. To specify a port number use the following format for the <hostname> parameter: "hostname:port".
Print out error messages for errors with agenda entries in the past. By default, only errors found with entries in the future are reported.
<user>
List users found in the backup file. Use the <user> option to restrict the list to certain users only. Specify users by providing the <user> argument. See FORMAT OF THE <user> ARGUMENT for details.
<node-ID>
Specify the node. Always required.
Do not update other users' agendas with changes to meetings that the user does not own but was invited to.
<sysOpPsw>
Provide the SYSOP password for the node. If you do not use this option, unirestore
prompts for the password.
<path>
Specify the path to the backup database files directory.
<uid>
Specify the user's UID.
Print the current version number of unirestore
.
Print a usage message explaining how to run unirestore
.
unidbbackup
% unirestore -ls "UID=smithj" -path "/backups/cserver/jan0799" -p abcdef12 -n 10 -host hubert3
% unirestore -u "smithj" -path "/backups/cserver/jan0799" -noAddAttendee -host hubert3 -p abcdef12 -n 10
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unirmold
- Remove old events and tasks from agendas in a calendar server database.
unirmold [-u <user>] [-d <numOfDays>] [-y] [-event] [-task] [-attachment] [-include <types>] [-sync] -n <node-ID> [-p <sysOpPsw>] unirmold -resource [<resource>] [-d <numOfDays>] [-y] [-attachment] -n <node-ID> [-p <sysOpPsw>] unirmold -v unirmold -h
unirmold
removes events and/or tasks older than a specified number of days from user or resource agendas in a calendar server database.
To remove an event from a user's agenda, unirmold
"un-invites" the user to the event. This has two consequences: the event no longer appears in that agenda AND the user no longer appears on the list of users invited to the event. The update to the list of invitees propagates as necessary to the other nodes in the node network.
By default, unirmold
removes all events and tasks older than 90 days from all user agendas in the node and all events older than 90 days from all resource agendas in the specified node. The -resource option restricts unirmold
to events in resource agendas. The <user> argument restricts unirmold
to the agendas of the specified users. See FORMAT OF THE <user> ARGUMENT for details on how to specify <user>.
When using unirmold
in -resource mode, you may specify a resource filter using the <resource> argument to restrict the deletion to certain resources only. See FORMAT OF THE <resource> ARGUMENT for details on how to specify <resource>.
Note:
|
unirmold
only runs if the calendar server is up.
Delete event attachments only. Use this option to remove the event attachments only and leave the rest of the events intact.
Delete events only. By default unirmold
deletes both events and tasks from the user agenda. Use the -attachment to only remove event attachments.
<types>
Delete events which are special types of agenda entries. Currently this option applies only to events which are either Outlook journal entries or sticky notes. The <types> argument is one or more of the following: journal
, sticky
. For example, to delete both types which are journal entries and sticky notes, use -include journal sticky
. To delete only events which are sticky notes, use -include sticky
.
<numOfDays>
Delete events and tasks that are more than <numOfDays> days old from the agenda. If you do not use this option, the default value is 90 days. The minimum value is 30 days.
<node-ID>
Specify the node. Required if more than one node exists on the host.
<sysOpPsw>
Provide the SYSOP password for the node. If you do not use this option, unirmold
prompts for the password.
<resource>
Remove all events in resource agendas only. You may specify a filter to select specific resources by providing the <resource> argument. See FORMAT OF THE <resource> ARGUMENT for details.
Removes all synchronization records from the user agenda.
Delete only tasks from the user agenda. By default unirmold
deletes both events and tasks from the user agenda.
<user>
Remove entries from the specified user agendas only. Specify users by providing the <user> argument. See FORMAT OF THE <user> ARGUMENT for details.
Used to auto-confirm the deletions.
Print the current version number of unirmold
.
Print a usage message explaining how to run unirmold
.
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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
The <resource> 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. For all keys except the ID key, 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/G=James\/Jim"
.
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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note that if the ID key-value pair is specified in the <resource> argument, all other key-value pairs specified along with it are ignored.
Key | Field |
---|---|
|
Resource name |
|
Resource number |
|
Identifier |
% unirmold -n 10
% unirmold -u "s=wembley" -event -d 30 -n 10
% unirmold -u "s=Smith/g=John" -attachment -d 360 -n 10
% unirmold -resource -d 30 -n 10
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unirndel
- Delete a remote node from a local calendar server node database.
unirndel -rn <node-ID> [-p <sysOpPsw>] [-n <node-ID>] unirndel -v unirndel -h
unirndel
deletes all references to a remote node from the database of a local node. By default the local node is the one with the name "N1". unirndel
should only be used to delete a remote node created for test purposes. You should consult Oracle Support before using unirndel
.
It is recommended that you back up the local $ORACLE_HOME/ocal/db
directory before running unirndel
.
unirndel
runs only if the calendar server is up.
<node-ID>
Specifies the node-ID of the local node database from which the remote node should be deleted.
<node-ID>
Specifies the node-ID of the remote node.
Print the current version number of unirndel
.
Print a usage message explaining how to run unirndel
.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unirnsynch
- Propagate deletions in the local information of one node to another node in the network.
unirnsynch -rn <node-ID> [-rhost <hostname>] [-rp <rSysOpPsw>] -n <node-ID> [-host <hostname>] [-p <sysOpPsw>] unirnsynch -v unirnsynch -h
unirnsynch
is used to propagate deletions in the local information of one node to another node in the network. Each node in a node network contains both local information and remote node information, where:
The remote node information of a given node is constructed from the local information of each of the other nodes in the node network.
Changes to the local information of a node are normally automatically propagated to all remote nodes in the network. However, if for any reason discrepancies do occur, the remote node information can be updated using unirnsynch
and/or uninode
. uninode
(using the -apply option) may be used to add missing entries while unirnsynch
is used to delete entries which no longer exist in the local information.
uninode -cws -group all
may be used to determine whether or not discrepancies exist (see the IMPORT-DIR field of the output).
The calendar server must be up to run unirnsynch
.
<hostname>
Specify the host where the node that has had deletions to local information resides. To specify a port number use the following format for the <hostname> parameter: "hostname:port".
<node-ID>
Specify the node-ID of the node that has had deletions to its local information.
<sysOpPsw>
Provide the SYSOP password of the node that has had deletions to its local information.
<hostname>
Specify the host where the node that is to have its remote node information updated resides. Default is the local host. To specify a port number use the following format for the <hostname> parameter: "hostname:port".
<node-ID>
Specify the node-ID of the node that is to have its remote node information updated.
<remote-sysOpPsw>
Provide the SYSOP password of the node that is to have its remote node information updated.
Print the current version number of unirnsynch
.
Print a usage message explaining how to run unirnsynch
.
% unirnsynch -rn 20 -rhost salt -rp remote-sysOpPsw -n 30 -host pepper -p sysOpPsw
Exit values are:
0 Success
1 Usage error
2 System error
uninode
unisizeof
- Compute the size of the calendar server installation.
unisizeof [-db | -n <node-ID>] unisizeof -v unisizeof -h
unisizeof
computes the size of a calendar server installation. By default, it determines the size of the $ORACLE_HOME/ocal
directory, including all database nodes and the calendar server (executables, *.ini
files, etc.). Use the -db option to determine the size of the entire database and the -n option to determine the size of a single database node.
unisizeof
runs whether the calendar server is up or down.
Compute the size of the entire database. The entire database is made up of all nodes on the server.
<node-ID>
Compute the database size of the specified node.
Print the version number of unisizeof
.
Print a usage message explaining how to run unisizeof
.
% unisizeof unisizeof: total size of the calendar server 44216K
% unisizeof -db unisizeof: total size of the calendar server database is 10010K
% unisizeof -n 10 unisizeof: database size for nodeid [10] is 760K
$ORACLE_HOME/ocal/misc/unison.ini
Used to determine the default node (i.e. the node for which "name = N1" in this file) when unisizeof
is used with the -db option.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unislice
- Extract information from the calendar server's log files.
unislice <logFile(s)> [-s <starttime>] [-e <endtime>] unislice -v unislice -h
unislice
extracts information from the specified log file(s) and sends it to standard output. The unisnapshot
utility uses unislice
to gather information contained in log files. The <logFile(s)> argument is a list of one or more log files; each must be a fully-specified path name separated from the others by a space. unislice
can run on most of the log files in the $ORACLE_HOME/ocal/log
directory.
unislice
runs whether the calendar server is up or down.
<endtime>
Set an end time. Only log file information with time stamps prior to this time are included in the output. Thus, if an end time of January 1 is set, no information from the 1st of January is included. See FORMAT OF starttime, endtime ARGUMENTS for details on how to specify these arguments.
<starttime>
Set a start time. Only log file information with time stamps on or after this time are included in the output. See FORMAT OF starttime, endtime ARGUMENTS for details on how to specify these arguments.
Print the current version number of unislice
.
Print a usage message explaining how to run unislice
.
Each of these arguments can take one of the forms:
where
is a number between 1 and 31;
is either the full name of the month or one of the following abbreviations: jan, feb, mar, apr, aug, sep, sept, oct, nov, dec (month is case-insensitive);
is specified using four digits; and
is in the form HH:MM or HH:MM:SS (HH is an integer between 0 and 23).
uniengd
log file:
% unislice $ORACLE_HOME/ocal/log/eng.log
uniengd
messages logged on February 7th 1995:
% unislice $ORACLE_HOME/ocal/log/eng.log -s 7 feb 1995 -e feb 8 1995
eng.log
messages after 1 PM, July 7:
% unislice $ORACLE_HOME/ocal/log/eng.log -s july 7 13:00
eng.log
messages before 9 AM, October 15, 1995:
% unislice $ORACLE_HOME/ocal/log/eng.log -e oct 15 9:00 1995
eng.log
messages logged in a 45-second period starting at 10 AM, January 30:
% unislice $ORACLE_HOME/ocal/log/eng.log -s jan 30 10:00:00 -e jan 30 10:00:46
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unisnapshot
unisnapshot
- Compile calendar server information for diagnostic purposes.
unisnapshot [<date>] [-nolog] [-p <sysOpPsw>] unisnapshot [-s <starttime>] [-e <endtime>] [-nolog] [-p <sysOpPsw>] unisnapshot -v unisnapshot -h
unisnapshot
assembles information used by support staff to diagnose most calendar server problems. Should a problem ever arise, only this file need be supplied to support staff.
Output is written to the unisnapshot.log
file in the $ORACLE_HOME/ocal/log
directory. unisnapshot
can be restricted to include log file information logged during a single day, or during a specified time period. This reduces the amount of irrelevant information in the output.
Under Windows operating systems, unisnapshot
requires the SYSOP password for each node. See the -p option for more information.
See FORMAT OF THE date ARGUMENT for details on how to specify <date>.
unisnapshot
can be run whether the calendar server is up or down.
<endtime>
Set an end time. Only log file information with time stamps prior to this time are included in the output of unisnapshot
. Thus, if an end time of January 1 is set, no information from the 1st of January is included. <endtime> is a string of the same format as <date>.
Prevent unisnapshot
from including log file information in its output.
<sysOpPsw>
This option exists only under Windows operating systems. Specify the SYSOP password to use to connect to each node. If you use this option, the SYSOP password must be the same for all nodes. If you do not use this option under Windows, unisnapshot
prompts for the SYSOP password for the first node at the time it connects to that node. For each subsequent node, it prompts for the SYSOP password only if the SYSOP password for that node is different from the last SYSOP password entered.
<starttime>
Sets a start time. Only log file information with time stamps on or after this time are included in the output of unisnapshot
. <starttime> is a string of the same format as date.
Print the current version number of unisnapshot
.
Print a usage message explaining how to run unisnapshot
.
The date argument takes one of the forms:
where
is a number between 1 and 31;
is either the full name of the month or one of the following abbreviations: jan, feb, mar, apr, aug, sep, sept, oct, nov, dec (month is case-insensitive);
is specified using four digits; and
is in the form HH:MM or HH:MM:SS (HH is an integer between 0 and 23).
If no year is specified, the default is the current year.
% unisnapshot
% unisnapshot -nolog
% unisnapshot 7 feb 1998
% unisnapshot -s july 7 13:00
% unisnapshot -e oct 15 9:00 1998
% unisnapshot -s jan 30 10:00:00 -e jan 30 10:00:46
$ORACLE_HOME/ocal/log/unisnapshot.log
This is the file where unisnapshot
writes its output. If a previous file exists at the time unisnapshot
is invoked, it is overwritten.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unisnapshot
may take some time to complete.
unisncdump
- Retrieve statistics from the calendar server's Synchronous Network Connection daemon/service.
unisncdump [-host <hostname>] [-n <node-ID>] [-p <sysOpPsw>] [-screen] unisncdump -v unisncdump -h
unisncdump
retrieves statistics from the unisncd
daemon and writes them to the $ORACLE_HOME/ocal/log/unisncdump.log
file. Included are the number of configured and available connections for each service.
<hostname>
Specify the host on which the unisncd
is located. To specify a port number use the following format for the <hostname> parameter: "hostname:port".
<node-ID>
Specify the calendar server node. Required if more than one node exists.
<sysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
Display the output on the screen instead of writing it to the log file.
Print the version number of unisncdump
.
Print a usage message explaining how to run unisncdump
.
unisncd
statistics for node 11 on host "oregano" to the screen (the node network contains two nodes: 11 and 12).
% unisncdump -screen -n 11 -host oregano Enter SysOp password: ----------------------------------------------- DATE = Mon Sep 28 14:50:08 1998 PID = 1314 Host = oregano Service = unieng,12 Transactions: Request = 0 Check Request = 0 Cancel Request = 0 Free = 0 Connections: Configured = 2 Available = 2 Granted = 0 Request queue = 0 Failed = 0 Last failure = 0 Next attempt = 0 Attempt timeout = 0 Max wait before retry = 3840
$ORACLE_HOME/ocal/log/unisncdump.log
unisncdump
writes to this file by default.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unistart
- Start up the calendar server or start a node.
unistart [-bypass] [-nocws] [-nosnc] [-nocsm] [-nodas] [-r] unistart -standby [-bypass] [-r] unistart -csmhost <host:port> [-p password] [-bypass] [-nocws] [-nosnc] [-nodas] [-r] unistart -n <node-Id> -csmhost <host:port> [-p password] unistart -n <node-Id> unistart -v unistart -h
unistart
is used to start a single node or to start the calendar server. The default action is to start all calendar server daemons or services that are not already started, these include: unilckd
, uniengd
, unidasd
(if a directory server is being used), unisncd
, unicwsd
and unicsmd
. To erase the contents of an old log file before a newly started daemon writes to it, use the -r option.
To start a single node, use the -n option. A node can be started only if the calendar server is already running.
A server (or a node) can be started remotely if the Calendar Server Manager daemon (unicsmd) is running for that server. To only start the unicsmd daemon, use the -standby option. To remotely start a calendar server or a node, use the -csmhost and -p options. If you have an installation with an Oracle Internet Directory, supply the SYSOP password, otherwise use the CSM password which is defined by the [CSM] password
parameter in unison.ini
.
The server can be started with some of the components left disabled using the options -nocws, -nosnc, -nocsm and -nodas.
By default, unistart
calls unicheck
to check the file system. You can skip this step by using the -bypass option.
By default, unicheck
is run before the daemons and services are started. This option causes unistart
to execute without running unicheck
.
Specify the host on which the remote unicsmd
is located. To specify the port number used by the unicsmd daemon (if the default port number is not used), use the following format for the <hostname> parameter: "hostname:csmport".
<node-ID>
Specify the calendar server node to start.
By default, unicsmd
is started (unless a [CSM] enable
parameter exists in unison.ini
and is set to "FALSE
".) This option overrides this and prevents unicsmd
from being started. unicsmd
can be brought up later by simply running unistart
again without this option.
By default, unicwsd
is started (unless a [CWS] enable
parameter exists in unison.ini
and is set to "FALSE
".) This option overrides this and prevents unicwsd
from being started. unicwsd
can be brought up later by simply running unistart
again without this option.
By default, unidasd
is started if the [DAS] enable
parameter in unison.ini
is set to "TRUE
". This option overrides this setting and prevents unidasd
from being started. unidasd
can be brought up later by simply running unistart
again without this option.
By default, unisncd
is started (unless a [SNC] enable
parameter exists in unison.ini and
is set to "FALSE
".) This option overrides this and prevents unisncd
from being started. unisncd
can be brought up later by simply running unistart
again without this option.
<password>
If you have an Oracle Internet Directory, provide the SYSOP password for the remote server. Otherwise you must supply the CSM password which is defined by the [CSM] password
parameter in unison.ini
. If this option is not used, prompting for the password occurs.
Removes any existing log files that will be used by the newly started components. The following table shows which log file is deleted when the component is started. Logs file are located in the $ORACLE_HOME/ocal/log
directory.
Component | Log files |
---|---|
|
cws.log |
|
snc.log |
|
das.log |
CSM |
csm.log |
LCK |
lck.log |
ENG |
eng.log, lck.log, dbv.log, act.log, utl.log, script.log, notify.log, utility.log |
Start the unicsmd daemon/service.
Print the current version number of unistart
.
Print a usage message explaining how to run unistart
.
unicheck
; remove the old log files at the same time:
% unistart -bypass -r
% unistart -nocws
% unistart -n 120 -csmhost hercules:7688 -p pass1
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unistat
- Produce a content report on a calendar server node.
unistat [-l] [-s | -g] [-m] -n <node-ID> [-p <password>] unistat -v unistat -h
unistat
produces a report for the specified node and sends it to standard output. unistat
prompts the user for the SYSOP password for the node. The following information is included in the report:
The calendar server must be up for unistat
to run.
Only print the list of public and administrative groups.
Print the report in 128 characters per line mode. If this option is not used, the default is 80 characters per line.
Print the members of the groups.
<node-ID>
Specify the node.
<sysOpPsw>
Provide the SYSOP password. If this option is not used, prompting for the password occurs.
Only print the user, resource and event calendar database statistics.
Print the current version number of unistat
.
Print a usage message explaining how to run unistat
.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unistats
- Display summary statistics of the data from a calendar server stats file.
unistats [-s <starttime>] [-e <endtime>] [-f <filename>] [-server <version>] [-client <entry>] [-n <node-ID>] [-user <user> | -res <resource> | -reserved] [-all] unistats -v unistats -h
Displays summary statistics of the data found in a calendar server stats file. By default, the input file is $ORACLE_HOME/ocal/log/stats.log
. The -server, -client, -n, -user, -res, -reserved filter options may be used to compile statistics from a subset of the information found in the stats file.
The default output is a summary for each unique calendar client. Different versions of the same client are treated as separate clients, and a summary is output for each.
The -all option displays a summary incorporating all clients. All output is displayed in 122-character-wide format. A complete list of all output fields is given in the OUTPUT section.
Display summary incorporating all interface clients.
<entry>
Display summary statistics on a specific calendar client. <entry> is the name and version of that client. See FORMAT OF THE entry, name, AND resource ARGUMENTS for details on how to specify <entry>.
<endtime>
Specify end time for statistics. If this option is not used, the default is the current time of the current day of the current month of the current year. See FORMAT OF THE time ARGUMENT for details on how to specify <endtime>.
<filename>
Specify the file to be used as input. This file must be in the same format as the default input file $ORACLE_HOME/ocal/log/stats.log
. This option is commonly used where a file has been created from an existing stats.log
file and is supplied as input to unistats
.
<node-ID>
Display summary statistics on a specific node. <node-ID> is a calendar server node-ID.
<resource>
Display summary statistics on a specific resource. <resource> is the name and/or identification number of the resource. See FORMAT OF THE entry, name, AND resource ARGUMENTS for details on how to specify <resource>.
Display summary statistics on all reserved users (e.g. SYSOP).
<starttime>
Specify a start time for the statistics. If this option is not used, the default start time is "Jan 1 1991 00:00:00". See FORMAT OF THE time ARGUMENT for details on how to specify <starttime>.
<version>
Display summary statistics on a specific calendar server. <version> is the version number of that server (e.g. A.02.90).
<name>
Display summary statistics on a specific user. <name> is some combination of the surname, given name, and organizational units of the user. See FORMAT OF THE entry, name, AND resource ARGUMENTS for details on how to specify <name>.
Print the current version number of unistats
.
Print a usage message explaining how to run unistats
.
Each of the arguments <entry>, <name>, and <resource> 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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note that if the ID key-value pair is specified in the -res argument, all other key-value pairs specified along with it are ignored.
Some example specifications are:
-client "N=Windows Oracle Calendar - 32 Bit/V=version 4.1" -user "S=Carter/G=Angela" -res "R=laptop" -res "ID=328"
The <starttime> and <endtime> arguments may be expressed as either:
where
The order of the individual elements in the argument is unimportant. What is important is that either day and month be specified, or time be specified. The following are all valid examples:
Feb 22 1996 10:00:00 22 february 10:00:00 10:00:00 february 22 1996 1996 feb 22 feb 22 10:00:00
Default values for <day>, <month>, <year>, and <time> are the current day, current month, current year and current system time respectively.
Any missing field in <time> (HH, MM, or SS) is replaced with the current HH, MM, or SS value. E.g. if the current date and time is March 12 1998 10:41:34, and only HH:MM are specified in the argument, the SS becomes "34":
-e 12:41 -> March 12 1998 12:41:34 -s 12:41 -> March 12 1998 12:41:34
If none of the time fields are specified, <starttime> defaults to the first minute of the day, and <endtime> defaults to the last minute of the day:
-s feb 22 -> feb 22 1998 00:00:00 -e feb 22 -> feb 22 1998 23:59:59
All output fields displayed by unistats
are explained here, in the order in which they will be seen:
$ORACLE_HOME/ocal/log/stats.log
):
% unistats
myfile.log
:
% unistats -client "N=window*" -f myfile.log
% unistats -user "s=martin/g=don" -server "A.02.90"
% unistats -res "R=projector/ID=901" -client "N=Motif"
% unistats -s jul 19 -e jul 19
% unistats -all -user "S=*"
% unistats -reserved -n 70
$ORACLE_HOME/ocal/log/stats.log
By default, unistats
obtains its information from this file. The [ENG] stats
parameter in unison.ini
must be set to "TRUE
" to enable uniengd
to log information to this file.
$ORACLE_HOME/ocal/log/unistats.log
unistats
logs any errors in this file.
Exit values are:
0 Success
1 usage error
2 system error
unistatus
- Determine the status of the calendar server and nodes.
unistatus [-f] [-d] [-s] [-cws] [-lck] [-reset] [-q] [-w] [-e] unistatus -csmhost <host:port> [-p <password>] [-f] [-d] [-s] [-cws] [-lck] [-reset] [-q] [-w] [-e] unistatus -n [<node-Id>] unistatus -csmhost <host:port> [-p <password>] -n [<node-ID>] unistatus -v unistatus -h
By default unistatus
determines which of the calendar server daemons/services are running and prints their current status to standard output. unistatus
can also be used to display the status of the nodes.
By default, unistatus will report the state of the calendar server as being up, partially up, down, in stand-by mode (the calendar server manager is running) or inconsistent and it will list any daemon or service that should normally be enabled but is not.
Many options are available for selecting various types of information to display. The -d, -f and -s options will display controllers, listeners, tasks and/or session information. See OUTPUT for the values and their meanings.
The quiet output (using -q) is useful when used in combination with the -e option, which returns a value that represents the state of the Calendar Server. This can be used by scripts to test whether the Calendar Server is up or not.
The -cws and -lck options will display extended statistical information on the unicwsd or unilckd daemons/services respectively. unistatus
will display the number of opened or closed database sessions, the number of database locks and the number of database commits. By default these counters will be reset to 0 once a day (this is configurable). The counters can also be reset manually using the -lck or -cws option in conjunction with the -reset option.
To run unistatus remotely, use the -csmhost and -p options. If connected to an Oracle Internet Directory, supply the SYSOP password, otherwise use the CSM password which is defined by the [CSM] password
parameter in unison.ini
of the remote server.
unistatus
runs whether the calendar server is up or down. To run unistatus remotely, the remote Calendar Server Manager (unicsmd) must be running.
Specify the host on which the remote calendar server is located. To specify the port number used by the unicsmd daemon (if the default port number is not used), use the following format for the <hostname> parameter: "hostname:csmport".
Display statistics for the corporate wide daemon/service (unicwsd).
Produce a report for task, listener and controller processes only.
Alter the default exit status values to provide information about the calendar server daemons/services. See EXIT STATUS for the values and their meanings.
Produce an extensive ps-like report, taking into account the distinction between listeners, sessions and controllers. The calendar server may have the following daemons and servers running:
uniengd
controller: always runningunilckd
listeners: always runninguniengd
listeners: always runninguniengd
sessions: when user processes are runningunicwsd
controller and tasks: runs if corporate-wide services are enabledunisncd
listener: runs if remote-node services are enabled and/or a directory server is being usedunidasd
listener and sessions: runs if a directory server is being usedunicsmd
listener: always runningDisplay statistics for the lock manager.
<node-ID>
Display statistics on a specific node.
<password>
With an Oracle Internet Directory, provide the SYSOP password for the remote server. Otherwise you must supply the CSM password which is defined by the [CSM] password
parameter in unison.ini
. If this option is not used, prompting for the password occurs.
Force the quiet version of the command which does not produce any output but returns the proper error.
Produce a report for sessions only.
Do not display messages for processes that are down or disabled, such as "CORPORATE-WIDE SERVICES are down" or "REMOTE-NODE SERVICES are down" when the unilckd
and uniengd
daemons/services are running but the unicwsd
or unisncd
daemons/services are not.
Print the current version number of unistatus
.
Print a usage message explaining how to run unistatus
.
For some platforms, certain values cannot be displayed. For instance, under NT there are no sessions and no controllers--only listeners will be shown. For Solaris, only controllers and listeners will be displayed. For AIX, the 3 classes will be shown. Output fields displayed by unistatus
:
% unistatus unistatus: The calendar server is partially up unistatus: the Calendar Corporate-Wide Services is down
% unistatus -f UID PID PPID STIME TIME COMMAND CLASS INFORMATION tin 6772 228 1:41:21 0:0:0.156 unisncd Listener tin 4368 228 2:32:23 0:0:0.187 unicwsd Controller 3 task(s) tin 6756 4368 2:32:27 0:0:0.125 unicwsd Task SSR tin 7680 4368 2:32:27 0:0:0.203 unicwsd Task Messaging tin 9444 4368 2:32:27 0:0:0.156 unicwsd Task Messaging,SSR,Snooze,EventSync,DirSync tin 7196 228 1:41:28 0:0:0.46 unicsmd Listener tin 6712 228 1:41:17 0:0:0.78 unilckd Listener 0 DB sess tin 6692 228 1:41:18 0:0:1.875 uniengd Listener 3/100 sess unistatus: the calendar server is up
The default exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
Use of the -e option alters the default exit values to encode the status of the various calendar server daemons/services. These values are as follows:
unistop
- Shut down the calendar server or a node.
unistop [-bypass] [-standby] [-cws] [-snc] [-das] [-csm] [-y] unistop -csmhost <host:port> [-p <password>] [-bypass>] [-cws] [-snc] [-das] [-nostandby] [-y] unistop -n <node-Id> [-y] unistop -n <node-Id> -csmhost <host:port> [-p <password>] [-y] unistop -clean [-force] unistop -v unistop -h
unistop
shuts down all or part of a running calendar server. By default, all daemons and services are shut down: unicwsd
, unisncd
, unidasd
(if a directory server is being used), uniengd
, unilckd
and unicsmd
. unistop
can also be used to stop a node or to clean up the system resources allocated by the server.
If any users are currently signed-on, unistop
prompts for confirmation before proceeding with the shutdown. Use the -y option to auto-confirm this confirmation.
To stop a single node, use the -n option. A server (or a node) can be stopped remotely if the Calendar Server Manager daemon (unicsmd) is running for that server. By default, on a local server, all components of the server are stopped. To leave the unicsmd daemon running, use the -standby option, this will allow you to restart the server remotely.
To remotely stop a calendar server or a node, use the -csmhost and -p options. If you have an installation with an Oracle Internet Directory, supply the SYSOP password, otherwise use the CSM password which is defined by the [CSM] password
parameter in unison.ini
. When stopping a server remotely, the unicsmd daemon is not stopped by default. You can force it to be stopped using the -nostandby option.
Specific components of the server can be stopped using the options -cws, -snc, -csm and -das.
Once the server is stopped, resources, possible leaks and any temporary files are removed. unistop
can be executed with the -clean option when the server is completely down to perform this cleanup. However, if for some reason unistop
thinks that the server is still up (for example when IPC or other resources are still lingering), you can force a clean operation using the -force option.
unistop
can only be run if the calendar server is at least partially up (i.e. one or more daemons are running).
unistop
cannot run at the same time as unistart
or another unistop
unless you use the -bypass option. This option might be useful if unistart
was abruptly terminated but is still detected as running.
Allow unistop
to execute even if another unistart
or unistop
process is running. Use this option with care, and always verify that unistart
is indeed not running before specifying this option.
Clean the system resources allocated by the server. The server must be shut down completely to use this option. If the server cannot be shut down for unknown reasons, try unistop -y -bypass,
or use the -force option.
Shut down only the Calendar Server Manager daemon/service (unicsmd
).
Specify the host on which the remote unicsmd
is located. To specify the port number used by the unicsmd daemon (if the default port number is not used), use the following format for the <hostname> parameter: "hostname:csmport".
Shut down only the Corporate-Wide Services (unicwsd
). The unilckd
and uniengd
daemons/services must be running for this option to succeed. To avoid problems, you should also be certain that unisncd
and unidasd
(if you are running a Directory Server) are both running.
Stop only the unidasd
daemons and servers. These are used only with a directory server. The unilckd
and uniengd
daemons/services must be running for this option to succeed. To avoid problems, you should also be certain that unicwsd
and unisncd
are both running.
Use in conjunction with the -clean option to force a clean up of the system resources allocated by the server, even if the server is up. This is normally not necessary and should only be used as a last resort.
<node-ID>
Specify the calendar server node to stop.
Stop the remote unicsmd
daemon. This option is used, when stopping a remote server, to force the remote unicsmd
to stop as well. The remote server will no longer be assessible remotely.
<password>
If you have an Oracle Internet Directory, provide the SYSOP password for the remote server. Otherwise you must supply the CSM password which is defined by the [CSM] password
parameter in unison.ini
. If this option is not used, prompting for the password occurs.
Shut down only the unisncd
daemon. The unilckd
and uniengd
daemons must be running for this option to succeed. To avoid problems, you should also be certain that unidasd
(if you are running a Directory Server) is running and unicwsd
is not running. This will also shut down unicwsd
.
Leave the unicsmd daemon running. Use this option so that after stopping a local server, you can restart it remotely.
By default, if there are any users signed on to the calendar server, a prompt is issued to confirm that a shutdown is desired. This option causes unistop
to automatically proceed with the shutdown even if there are users signed on. The shutdown of each of the active uniengd
servers proceeds in such a way as to ensure the integrity of the database.
Print the current version number of unistop
.
Print a usage message explaining how to run unistop
.
% unistop
% unistop -cws
% unistop -n 44 -csmhost hubert:8804 -p pass1
% unistop -das
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unistrconv
- Convert text to UTF-8 or to another character set.
unistrconv [-from <charset>] [-to <charset>] -s <string> unistrconv [-from <charset>] [-to <charset>] -s <string> [-y] -if <inputFile> -of <outputFile> unistrconv -v unistrconv -h
Converts text from one character set to another. By default, the string is converted to UTF-8. The text can be read from a file and output to another file.
Use this utility to convert text to be used as the banner for e-mail messages which must be provided in UTF-8 format.
<charset>
Specify the character set to convert from. By default, the current character set is used. Valid values for <charset> include:
English:
Brazilian Portuguese, French, German, Italian:
Japanese:
Korean:
Simplified Chinese:
Traditional Chinese:
Specifies the path name of the file containing the text to be converted.
Specifies the path name of a file which will contain the converted text.
<string>
Specify the string to be converted.
<charset>
Specify the character set to convert to. By default, the UTF-8 character set is used. See the -from option for valid values for <charset>.
Used with the -of option to auto-confirm the overwriting of the output file.
Print the current version number of unistrconv
.
Print a usage message explaining how to run unistrconv
.
% unistrconv -if bannerMsg.txt -of bannerMsgUtf8.txt unistrconv: File has been converted successfully.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unisyncrefresh
- Refresh calendar server sync records.
unisyncrefresh [-n <node-ID>] [-host <hostname>] [-fr <date>] [-p <SYSOPpassword>] unisyncrefresh -v unisyncrefresh -h
unisyncrefresh
refreshes the calendar server synchronization records.
With the new version of the calendar server, it is no longer necessary to run unisyncrefresh periodically, as the CWS now ensures that the sync information stays up to date.
unisyncrefresh can only be run if the calendar server is up.
<date>
Force a rebuild of all sync information newer than the given date. Should be used only in cases of corruption of the synchronization records, not during normal maintenance. Some end users may need to recreate their sync contexts to see any benefits. Consult Oracle support for instructions on using this option in specific circumstances. The format of the date is mm/dd/yyyy.
<hostname>
Specifies a host which contains the node specified by the -n option. Required if connecting to a remote host. If -host is not present, unisyncrefresh
will assume the local host. If -host is specified and -n is not, unisyncrefresh
will search for a master node on the specified host.
<node-ID>
Specify a node. If -n is not used, unisyncrefresh
will search for a master node located on the host specified by the -host option. If no master node exists, -n is required.
<SYSOPpassword>
Provide the SYSOP password for the specified node. If this option is not used, unisyncrefresh
will prompt for the password.
Print the current version number of unisyncrefresh
.
Print a usage message explaining how to run unisyncrefresh
.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
unitzinfo
- Print time zone information.
unitzinfo [-c] [-l] [-t <timezone>] [-node <node-ID>] [-y <year>] unitzinfo -v unitzinfo -h
Extracts information from the calendar server time zone table found in the $ORACLE_HOME/ocal/misc/timezone.ini
file. By default, the information for the configured time zone, for the current year, used by the calendar server is printed in an 80-character-wide format.
The calendar server table contains time zone information from the year 1991 to 2074 inclusive.
unitzinfo
can be run whether the calendar server is up or down.
List the time zone information by country. Time zones within a country are listed in sequence. The printed fields are:
Print the information in 132-character-wide ("large") output format.
<node-ID>
Specify the node. This option causes the information for the time zone configured for the node to be output.
<timezone>
Specify the name of the time zone to print. If timezone has the value "all", the complete list of time zones is printed.
<year>
Specify the year for which the time zone information will be output (e.g. to view the DST period for that year). <year> must be specified using four digits. The default is the current year.
Print the current version number of unitzinfo
.
Print a usage message explaining how to run unitzinfo
.
% unitzinfo -node 20 EST5EDT Eastern Standard Time, Eastern Daylight Time U.S.A. (Eastern), Canada (Eastern), Bahamas, Haiti, Turks & Caicos Hours from GMT: -5h Daylight Saving Time : -4h (Apr 4,1999 - Oct 30,1999)
$ORACLE_HOME/ocal/misc/timezone.ini
This file contains the time zone descriptions used by the calendar server.
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniuser
- List, add, or delete calendar users, resources or event calendars, modify the information associated with them or transfer data from one user to another.
uniuser -ls [<user>] [-format <format>] [-host <hostname>] -n <node-ID> [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]] [-ext] [-showdefault] uniuser -defaultls [-s <section>] [-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]] uniuser -inactivels <date> [-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]] [-ext] [-showdefault] uniuser -newls <date> [-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]] [-ext] [-showdefault]
uniuser -add <filter> [-s <section>] [-host <hostname>] -n <node-ID> [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]]
uniuser -del <filter> [-y] [-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]] uniuser -desdel -u <filter> [-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]] uniuser -grpdel -u <filter> [-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]]
uniuser -mod <filter> -s <section> | -m <modifier> [-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]]
uniuser -ex <filename> [-s <section>] [-y] [-k] [-user | -resource | -eventcal] [-host <hostname>] [-n <node-ID>] [[-p <psw>] [-uid <uid>] | [-krb]] uniuser -edit <filter> [-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]]
uniuser -transfer <filter> -u <targetfilter> [-host <hostname>] [-n <node-ID>] [[-event <filter>] | [-group <filter>]| [-task <filter>]| [-folder <filter>]] [-user | -resource] [[-p <psw>] [-uid <uid>] | [-krb]] uniuser -info [<attribute>][-host <hostname>] [-n <node-ID>] [-user | -resource | -eventcal] [[-p <psw>] [-uid <uid>] | [-krb]] uniuser -v uniuser -h [command]
uniuser
can list, add, or delete calendar users, resources or event calendar accounts, or modify the information associated with them. You must specify the type of account (user, resource or event calendar) by choosing one of the three options: -user, -resource or -eventcal. These options determine which configuration (user.ini
, resource.ini
or eventcal.ini
) file will be used when needed. Before modifying an account with the -mod option, the -info <attribute> can be used to verify which attributes can be modified and what are the valid values for one attribute in particular.
Uniuser can also be used to transfer calendar data from one user or resource to another using the -transfer option.
The information associated with a calendar user is a combination of the key-value pairs described in the FORMAT OF THE <user> ARGUMENT, and the information contained in the user.ini
file. This includes user preferences, security, administrative rights, X.400 information, personal group, admin group membership and the list of persons permitted to work as a designate for the user, etc.
Resources are identified by their names so each must be unique. The information associated with a resource is a combination of the key-value pairs described in the FORMAT OF THE <resource> ARGUMENT and the information contained in the resource.ini
file (which includes the resource preferences, security, personal group, admin group membership, and the list of users permitted to work as a designate for the resource).
Event calendars are also identified by their names. See how to specify an event calendar in the table FORMAT OF THE <eventcal> ARGUMENT.
Note that the -ls, -add, -del, -grpdel, -desdel, and -mod options are all mutually exclusive.
It is recommended that you use uniuser
to modify only user attributes that are specific to the calendar server. Any attributes that can be modified using the Oracle Internet Directory administration tools directly should not be modified through uniuser
.
The calendar server must be up to run uniuser
.
filter: <user> / [<resource>] / [<eventcal>]
Use this command to create a new calendar user, resource or event calendar. The information associated with the new account is a combination of what is specified in the <user> argument and the default values in the configuration file (user.ini
, resource.ini
or eventcal.ini
files). By default, when uniuser
reads the configuration file, it considers only the values in the [GEN]
section. Use the -s option to apply values from other sections of the configuration ini file. Use the -ex option to add multiple users, resources or event calendars.
Mandatory attributes must be provided otherwise the attempt to add a new account will fail. For example, when adding an event calendar or a resource, the name and password must be supplied with the "N" and the "PSW" keys. When using the calendar server's internal directory (no external directory), the "S" key is mandatory for the -add option for adding a user.
For external directories, users must already exist in the directory server. The DID (Directory ID) for the user must be specified, and it must be in DN (Distinguished Name) format. This can be followed by data in X.400 format. See EXAMPLES.
Use this command to list the default attribute values for the specified user, resource or event calendar. The values will be taken from the configuration file section defined by the -s option.
filter: <user> / [<resource>] / [<eventcal>]
Use this command to delete the calendar user, resource or event calendar specified by <user>. uniuser
prompts for confirmation before performing the deletion unless the -y option is used. If more than one account is to be deleted, the -ex option must used.
This operation can take a long time for very large agendas, and may have an impact on the performance of the calendar server for other users. It is recommended that you only delete users in off-peak hours.
Use this command to delete all designate rights that the user specified by the -u option has. If more than one match for the user is found in the database, uniuser
fails. A node must be specified using the -n option. Only the designate rights to agendas residing on the specified node will be revoked. To delete all designate rights of the user, you must run this command on all connected nodes. For example: Bob Smith is on node 1, Mary is on node 2 and Jack is on node 3. Mary gives designate access to her agenda to Bob and Jack gives designate rights to his agenda to Bob. The command "uniuser -desdel -u "S=Smith/G=Bob" -n 2
" will revoke the designate access that Bob has to Mary's agenda but not to Jack's.
filter: <user> / [<resource>] / [<eventcal>]
This command only exists under UNIX. It allows you to first output the list of existing calendar users to a file, then edit the file to make desired modifications, and finally to input the changes back into the node.
The uniuser -edit command will open a file editor command (notepad on NT, vi on Unix). When the editor opens, you will see that the file will be populated with all the accounts that match the user filter defined by <user>. You can then edit the file, adding delete or modify symbols, as described for the -ex option. When you will save and close the file, uniuser will process the file as if the -ex option had been specified.
The following sequence of commands is automatically performed:
% uniuser -ls -n node-ID > file % vi file % uniuser -ex file -n node-ID % rm file
<filter>
Use with the -transfer option to transfer agenda entries such as meetings, notes, daily events and journals from one calendar account to another. Use the <filter> argument to specify the type of agenda entries that will be transferred. Limit the number of entries to be transferred by using the key "TIMEINTERVAL
". Only entries within the specified time range will be transferred. If not time interval is specified, all entries will be transferred.
The <filter> 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 "true
" or "false
" for all of the keys except the TIMEINTERVAL
value which must have the following format: "YYYY-MM-DD [HH:MM],YYYY-MM-DD [HH:MM]". Both "key" and "value" are case insensitive.
<filename>
Use this command to perform the additions, deletions, and/or modifications specified in the file <filename>. Each line of the file must begin with one of the characters `.', `#', `A', `a', `D', `d', `M', `m', `S', `s', `+'or `-'. This initial character specifies the action to take, as follows:
The initial character must be followed by a space and a user specification. In the case of a modification, the user must be specified in a first line starting with the letter 'M' or 'm'. This line is used to identify the user. The following line which starts with a '-' (minus sign) contains key-value pairs which will be applied as the modifications. See EXAMPLES.
For each deletion specified in the file, uniuser
prompts for confirmation before performing the deletion. The -y option is used to automatically provide confirmation.
One way to create this file is to save the output of uniuser -ls
to a file. This can then be edited and input to uniuser -ex
.
The -s sections option may be used with -ex to define which section of the configuration file is to be used when defining default values for the user information when modifying or adding users, resources or event calendars.
For directory servers, the most common way of adding many calendar users is to first use unidssearch
to output the list of all non-calendar users to a file. This file can then be modified (if necessary), and input to uniuser
using the -ex option. unidssearch
outputs in the same "key=value/key=value/..." format that uniuser
requires for input. See EXAMPLES.
Used with the -ls, -newls or -inactivels options, -ext will display the extended list of attributes. By default, only a subset of the user attributes are listed.
<filter>
Use with the -transfer option to transfer address books (contacts) from one user or resource to another. Address books cannot be transferred from event calendar accounts.
The <filter> 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 "true
" or "false
". Both "key" and "value" are case insensitive. For now, ALL is the only possible option which means that all the address book data will be transferred.
Key | Values | Definition |
---|---|---|
|
|
All types |
<format>
This option is used to select user information fields and to customize the format of the output. The -info option lists the parameters that can be used to specify the customized format. Some of these are also listed in the FORMAT OF THE <user> ARGUMENT section. If this option is not used, all user information fields are output, and a default presentation format is used. See EXAMPLES.
<filter>
Use with the -transfer option to transfer groups owned by one user to another.
The <filter> 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 "true
" or "false
". Both "key" and "value" are case insensitive. For now, ALL is the only possible option which means that all groups will be transferred.
Key | Values | Definition |
---|---|---|
|
|
All types |
Use this command to delete the specified user, resource or event calendar from all admin groups on the specified node. The user, resource or event calendar must be specified by the -u option. A single user, resource or event calendar must match <user> or the command fails. This command will only apply to the admin groups on the node specified by the -n option.
<hostname>
Use this connection option to specify the host which contains the node specified by the -n option. Required for remote hosts. If -host is not present, uniuser
will assume the local host. For modification or deletion, if -host is specified and -n is not, uniuser
will search for a master node on the specified host. If a master node is found, uniuser
will use it to locate the selected users.
<date>
Use this command to list the inactive accounts (users, resources or event calendars) since the specified date. The date format is "YYYY-MM-DD".
<attribute>
Use this command to list the attributes and format parameters used with the -format option. The list is generated dynamically by the server and may vary from one server to another depending on the server's setup. If a value for the <attribute> parameter is supplied, then only information on that attribute is displayed. The <attribute> value can be any attribute listed when the -info option is used alone (see EXAMPLES).
Used with the -ex option to force uniuser
to continue processing all lines in the file even if it encounters an error. Errors are sent to standard error; file redirection may be used to capture these to a file.
Use this authentication option to specify automatic Kerberos login. This option cannot be used with the -p and -uid options.
[
<filter>]
If a user is specified, the -ls command lists that user (in the specified node). If no user is specified, all users in the node are listed. The -format option can be used with -ls to configure the presentation of the output (see EXAMPLES).
<modifier>
Specify a modification to be made to the information of a particular user, resource or event calendar account. The modifier is a string of the same format as the <user> argument with the following exceptions for users: the ID key may not be specified. The PSW, PUBLISHEDTYPE and GLOBALREADONLY keys may be specified. Any attempt to modify read-only attributes will fail. For a more complete list of the keys and formats that can be used, use the -info option.
<user>
Use this command to modify the information associated with the specified user. This option is used with either the -s or the -m options. Use the -m option to specify directly which modifications to make to the user's information. When used with the -s option, the modifications are specified in a section of the configuration file (user.ini
, resource.ini
or eventcal.ini
).
<node-ID>
Use this connection option to specify a node. If -n is not used, uniuser
will search for a master node located on the host specified by the -host option. If a master node is found, uniuser
will use it to locate or distribute the specified users (except when a node must be specified using the -n option). If no master node exists, -n is required.
<date>
Use this command to list accounts (users, resources or event calendars) created since the specified date. The date format is "YYY-MM-DD".
<psw>
Provide the administrator's password with this authentication option; required if one is set. If this option is not used and a password is required, uniuser
prompts the user for it.
<sections>
Specify which section of the configuration file to use for determining the default values to be used for editing or adding calendar accounts. Which configuration file (user.ini
, resource.ini
or eventcal.ini
) will be used depends on the account type (-user, -resource, or -eventcal) specified.
See the -add and -mod options for information on using -s <sections> to apply values from the configuration file.
The <sections> argument is a list of one or more section names, each separated by a forward slash (e.g. "GEN/GR1/GR2" specifies the sections GEN, GR1 and GR2). Evaluation is done from left to right. Thus, in the preceding example, GEN is evaluated first, GR1 second, and GR2 last. Where the same key appears in more than one section, the value of the last instance evaluated takes precedence.
Used with the -ls, -newls or -inactivels options, -showdefault will display all attributes which are currently set to 0, FALSE or an empty string.
<filter>
Use with the -transfer option to transfer tasks from one user to another.
The <filter> 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 "true
" or "false
". Both "key" and "value" are case insensitive. For now, ALL is the only possible option which means that all tasks will be transferred.
Key | Values | Definition |
---|---|---|
|
|
All types |
<user>
Use this command to transfer calendar data ownership from one user or resource account to another. Only calendar entries that the user (or resource) owns can be transferred to the target user (or resource). Use the <user> argument to specify the user or resource whose data will be transferred. User the -u option to define the target calendar account which must be of the same type, and on the same node, as the <user> account (e.i. user or resource). See FORMAT OF THE <user> ARGUMENT for details on the <user> argument. Use the -event, -task, -group and -folder options to define which type of calendar data to transfer. Use the -y option to auto-confirm the transfer.
<user>
Used with the -target, -desdel and -grpdel options to specify a user, resource or event calendar. See FORMAT OF THE <user> ARGUMENT for details on the <user> argument.
<user-ID>
Specify the administrator's user ID with this authentication option. If no user ID is specified, the SysOp's is used.
Used with the -del and -ex options to auto-confirm the deletion(s). Used with the -transfer option to auto-confirm the transfer.
Print the current version number of uniuser
.
<command>
Print a usage message explaining how to run uniuser
. The <command> argument can be used to get help on one of the following commands: -ls, -info, -defaultls, -inactivels, -newls, -add, -del, -grpdel, -desdel, -mod, -transfer, -ex and -edit.
The <user> argument, which is used to represent a user, resource or event calendar, 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. For all keys except the ID key, 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 should be escaped (i.e. preceded by the escape character "\") to prevent the shell from interpreting them.
Note: If the ID key-value pair is specified in the user argument, all other key-value pairs specified along with it are ignored. |
The format parameters listed in the third column in the following table are used with the -format option to configure the presentation of a listing (see EXAMPLES). For a more complete list of the keys and formats that can be used, use the -info option.
Key | X.400 Field | Format Parameter |
---|---|---|
N |
Event calendar name |
%N% |
PSW |
Event calendar account password |
%PSW% |
Key | X.400 Field | Format Parameter |
---|---|---|
|
Resource name |
%R% |
|
Resource number |
%N% |
|
Resource unique identifier |
|
% uniuser -user -ls "s=W*" -n 23 Enter SysOp password: S=Whitman/G=Walt/ID=154/C=US S=Winterson/G=Jeannette/ID=114/C=England
% uniuser -user -ls "s=W*" -format "%s%:%g%" -n 23 Enter SysOp password: Whitman:Walt Winterson:Jeannette
% uniuser -user -format "%s%:%g%" -n 23 Enter SysOp password: Brossard:Nicole Dillard:Annie Jansson:Tove Kilpi:Eeva Kundera:Milan Lorde:Audre Morrison:Toni Sanchez:Sonia Whitman:Walt Winterson:Jeannette
% uniuser -resource -ls "R=HPLaser*" -n 12 Enter SysOp password: . R=HPLASER dorian/S=Wilde/G=Oscar/ID=438 . R=HPLASER sula/S=Morrison/G=Toni/ID=512
% uniuser -resource -ls "R=HPLaser*" -format "%r% Contact: %g% %s%" -n 12 Enter SysOp password: HPLASER dorian Contact: Oscar Wilde HPLASER sula Contact: Toni Morrison
% uniuser -user -add "S=Angelou/G=Maya" -n 24
% uniuser -user -add "DID=cn=Maya Angelou, o=Acme, c=US" -n 24
% uniuser -resource -add "R=oakroom/PSW=abcdef123" -n 12
[GEN]
section of the user.ini
file (Milan Kundera exists in node 23). Look at the values in the GEN section of the user.ini
file and ensure they are all valid:
% uniuser -user -defaultls -s "GEN" -n 23 StartDay = 08h00 EndDay = 18h00 TimeInc = 30 ShowSunday = FALSE ShowSaturday = FALSE TimeFormat = 2 RefreshFrequency = 60 DefaultReminder = 0 TimeBeforeReminder = 10 MailNotification = TRUE OU1 = OU2 = OU3 = OU4 = O = C = A = P = TimeZone = ViewNormalEvent = TIME ViewPersonalEvent = TIME ViewConfidentialEvent = TIME ViewNormalTask = NO ViewPersonalTask = NO ViewConfidentialTask = NO CanBookMe = TRUE
% uniuser -user -mod "S=Kundera/G=Milan" -s "GEN" -n 23
% uniuser -user -mod "S=Kundera/G=Milan" -m "ou1=authors" -n 23
Multiple additions, deletions, and modifications are done using the -ex option. In this example, three new calendar users are added, one modified, and one deleted. A directory server is being used.
% unidssearch > multiple.dat % cat multiple.dat A DID=cn=Italo Calvino,o=Acme, c=US A DID=cn=Herman Hesse,o=Acme, c=US A DID=cn=Doris Lessing,o=Acme, c=US A DID=cn=Anja Kauranen,o=Acme, c=US
% vi multiple.dat % cat multiple.dat A DID=cn=Italo Calvino,o=Acme, c=US/OU2=R&D A DID=cn=Herman Hesse,o=Acme, c=US A DID=cn=Doris Lessing,o=Acme, c=US A DID=Anja Kauranen,o=Acme, c=US M ID=154 - G=Walter D G=Nicole/S=Brossard
In the case of the modification, the ID is used to find the user, and the given name is modified to Walter.
uniuser
:
% uniuser -user -ex multiple.dat -n 23 Enter SYSOP password: uniuser: added "cn=Italo Calvino,o=Acme, c=US" uniuser: added "cn=Herman Hesse,o=Acme, c=US" uniuser: added "cn=Doris Lessing,o=Acme, c=US" uniuser: added "cn=Anja Kauranen,o=Acme, c=US" uniuser: modified "Whitman,Walt" uniuser: deleted "Brossard,Nicole"
Note that if this example did not use a directory server, the input file would contain the following:
% cat multiple.dat A S=Calvino/G=Italo/OU2=Sales A S=Hesse/G=Herman A S=Lessing/G=Doris A S=Kauranen/G=Anja M ID=154 - G=Walter D G=Nicole/S=Brossard
% uniuser -transfer "S=Angelou/G=Maya" -u "S=Wilde/G=Oscar" -n 24 -event "public=true/TIMEINTERVAL=2003-01-01,2003-12-31" -krb
% uniuser -transfer "S=Angelou/G=Maya" -u "S=Wilde/G=Oscar" -n 24 -event "normalevent=true/confidential=true/TIMEINTERVAL=2003-03-03,2003-03-07" -krb
% uniuser -transfer "S=Angelou/G=Maya" -u S=Wilde/G=Oscar -n 24 -task "all=true" -group "all=true" -krb
% uniuser -info -user -n 24 -p mypasswd DID EXTENDED string[1024] CATEGORY EXTENDED enum NODE-ID* BASIC number ID* BASIC number LOADBALANCING EXTENDED boolean ENABLE EXTENDED boolean REMINDER-SERVERSMS EXTENDED boolean REMINDER-LEADTIME EXTENDED duration [minute] ...
% uniuser -info -user PUBLISHEDTYPE -n 24 -p mypasswd Name: PUBLISHEDTYPE Rights: Create Update Read Remove View Level: BASIC Type: enum Acceptable value(s): NOTPUBLISHED PUBLISHED
$ORACLE_HOME/ocal/misc/user.ini
This file specifies possible calendar user configurations. See also the calendar server Reference Manual, Appendix A, "Calendar User and Resource Parameters".
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
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.
Deleting users with a large numbers of meetings and events can take a long time and cause a decrease in performance for other calendar users. It is recommended that you delete such users outside of normal hours, or at least not at times of peak calendar usage.
universion
- Display and verify the version of the calendar server.
universion [-all] [-nowarn] universion -v universion -h
universion
displays the version number of the calendar server and checks all scripts and binaries to see if their versions are up to date.
universion
runs whether the calendar server is up or down.
Display version number for each component of the calendar server.
Suppress warning messages.
Print the current version number of universion
.
Print a usage message explaining how to run universion
.
% universion
% universion -all
Exit values are:
0 Success
1 Failure
2 Usage error
3 Warning error
4 Severe error
5 Critical error
6 User interrupt
uniwho
- Display information on signed-on calendar users.
uniwho [-a] [-t] [-j] [-x] [-f] [-n node-Id] [-pattern <pattern>] [-nolist] [-nototal] uniwho -v uniwho -h
This utility allows the system manager to determine who is using the calendar server, where they are signed-on from, and the process-ID associated with their session. The options allow the display of various combinations of process-id, network address, node-ID, and user information. A connection summary will also be displayed indicating the total number of connections for standard (users, resources and event calendars), shared (Web client applications) and reserved (sysop, cwsop) connections. Use the -nototal option if you don't want to display the connection summary.
This information is essential in certain situations. For example, when a user has done an abnormal shutdown of a client (say a power down while their client is active) the associated server process for that client continues to remain active for a fixed period of time. If the calendar server is configured (via the [ENG] max_userlogons
parameter in unison.ini
) to limit the number of sessions per user to 1, this user will not be able to log on again until their server process had terminated. uniwho
allows the system manager to find the process-ID of the session and terminate it.
uniwho
can only be run if the calendar server is up.
Display the alias associated with the default network address.
Display telephone, job-title and X.400-address when available.
Display job-title when available.
<node-ID>
Restrict to users and resources on specified a node.
Do not display the list of users.
Do not display the connection summary.
<pattern>
Display information for sessions which contain <pattern> in their information. For example, the pattern "128.192.64.96" would result in the display of session information for those logged on from this IP address. Matching is performed on all fields (network address/alias, telephone number, job-title, X.400 address), regardless of which of these may have been specified on the command line.
Display telephone number when available.
Display X.400 address when available.
Print the current version number of uniwho
.
Print a usage message explaining how to run uniwho
.
% uniwho -a PID ALIAS NODEID XITEMID USER 2120 ark.boat.com 12 12,2 CWSOP,na 24091 sail.boat.com 12 12,316 Barnes,Pat,B 24298 row.boat.com 12 12,311 Beck,Tom,V TOTAL STANDARD SHARED CONNECTIVITY 3 2 0 1
% uniwho -pattern Quality PID ADDRESS NODEID XITEMID USER 24298 199.88.48.81 12 12,311 Beck,Tom,V TOTAL STANDARD SHARED CONNECTIVITY 1 1 0 0
% uniwho -f PID ADDRESS NODEID XITEMID USER 2120 199.88.48.6 12 12,2 CWSOP,na 24091 199.88.48.81 12 12,316 Barnes,Pat,B Engineer/R&D /barnesp@acme.com /738-1000/123 24298 199.88.48.85 12 12,311 Beck,Tom,V Technician QualityAssurance/QA /tomb@acme.com /738-2000/015
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt
uniwho
starts a calendar server process. If activity logging has been enabled (via the [ENG] activity
parameter in unison.ini
), the start-up and shutdown of this process is logged.