Skip Headers

Oracle Calendar Server Release Notes
Release 5.5

Part Number B10147-01

Oracle® Calendar Server

Release Notes

Release 5.5

August, 2002

Part No. B10147-01

This document summarizes the differences between the Oracle Calendar server and its documented functionality. For the most recent and up-to-date information on this product, consult the Oracle Collaboration Suite Release Notes Addendum, available online at http://otn.oracle.com.

1 Certification and System Requirements

Windows

one of the following operating systems:

UNIX

one of the following operating systems:

All Platforms

Note:

Up to 150 MB free disk space may be necessary for installation.

2 General Issues and Workarounds

This section describes general issues and their workarounds for the Oracle Calendar server.

2.1 One server instance per machine

Only one instance of the Oracle Calendar server may be installed on any one UNIX or Windows machine. You may be able to work around this limitation by using multiple calendar server nodes instead of multiple installations. Consult the Oracle Calendar Server Administrator's Guide for more information.

2.2 Oracle CorporateSync 2.1.4 for Palm, Macintosh Edition

If you plan to deploy Oracle CorporateTime 2.1.4 for Palm, Macintosh Edition in your organization, you must add the cs-basic authentication mechanism to the list of authentication mechanisms supported by the calendar server. In the /users/unison/misc/unison.ini file, find the [AUTHENTICATION] supported parameter, and add cs-basic to the list specified. For more information, see the Oracle Calendar Server Administrator's Guide, Appendix D, "Security."

2.3 Resource double-booking

It is not currently possible to configure some resources to allow double-booking and some not to allow double-booking, even by locating those groups of resources on different servers within the node network. The [ENG] allowresourceconflicts and [LIMITS] resourceconflicts parameters must be set to the same value for all servers in your installation.

3 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds for the Oracle Calendar server.

3.1 HP-UX 10.20 operating system patch

Before installing the Oracle Calendar server on an HP-UX 10.20 system, you must apply patch PHSS_15043 (or the newer version if this one is superseded). For HP-UX 11.0 systems, the necessary patch number is PHSS_16587 (or the newer version if this one is superseded). These patches can be downloaded from http://us-support.external.hp.com or http://europe-support.external.hp.com.

3.2 Solaris 2.6 operating system patch

The Oracle Calendar Server requires the C runtime library libCrun.so.1 on Solaris 2.6 platforms. This library is available in the latest Solaris 2.6 operating system patches at http://www.sun.com. The appropriate patch must be installed before installing the calendar server.

NOTE: Please DO NOT install the following patch:

If you have installed this patch, please unistall it and re-install the latest patch.

3.3 Tuning the Red Hat Linux kernel

Red Hat Linux Advanced Server release 2.1AS/i686 requires a change to the system kernel parameters in order to support the Oracle Calendar server's default configuration. Use the table below to determine the calendar server requirements for each parameter, where the value of X for each parameter is equal to its previous setting, and the value of N is equal to the value of the [LCK] lck_users parameter in the /users/unison/misc/unison.ini file (2500 by default)

Table 1 Kernel tuning requirements for Red Hat Linux Advanced Server
Parameter Description Calendar requirement New value

fs.file-max

Max number of open files

40 * N

(40 * N) + X

kernel.threads-max

Max number of processes

(2 * N) + 20

(2 * N) + 20 + X

kernel.msgmni

Max number of message queue IDs

N + 1

N + 1 + X

kernel.msgmnb

Max size of message queue

N + 1

N + 1 + X

kernel.sem(semmns)

Max number of semaphores

1

1 + X

kernel.sem(semmni)

Max number of semaphore IDs

1

1 + X

Note that the kernel.sem parameter is multi-valued, accepting a value of the format: 'semmsl semmns semopm semmni'. Only the semmni and semmns values (the second and fourth supplied to kernel.sem) need to be tuned for Oracle Calendar.

4 Administration Issues and Workarounds

This section describes administration issues and their workarounds for the Oracle Calendar server.

4.1 unimvuser utility and UID key

The unimvuser utility cannot move a user specified only by the UID key.

4.2 Moving users in node networks with master nodes

After using the unimvuser utility to move a user between nodes, there may be a delay before that user's new location is replicated to the master node. During this time, that user will not be able to sign in.

4.3 Event calendars and "Can invite me to events" setting

Event calendars should be created with "Can invite me to events" disabled by default. This does not occur using the Calendar Administrator.

4.4 Creating holidays on large nodes

Problems encountered when creating holidays on nodes with large user counts may be caused by the value of the [ENG] readlocktimeout and writelocktimeout parameters. Wait until after normal business hours, raise the parameter values, add the holidays, and when finished lower the parameters to their previous values.

4.5 [ACE_PLUGINS_CLIENT] web_attribute_valuemax parameter

The value of this parameter must be set two integers higher than the desired value.

4.6 unicpinr utility restrictions

Oracle Internet Directory requires that passwords be set at resource creation, which is not supported by the unicpinr utility. Consequently, unicpinr cannot be used to add a calendar resource. Create the resource separately, then use unicpinr to import any desired information.

5 Documentation Errata

This section describes known errors in the documentation.

5.1 unidbfix requires that the calendar server be down

Page 10-3 of the Oracle Calendar Server Administrator's Guide states: "The unidbfix utility should be run in check mode once a week with the calendar server running, and in fix mode once a month with the calendar server down." In fact, the unidbfix utility requires that the calendar server be down for both check and fix mode.

5.2 [LDAP] certdbpath parameter

The /users/unison/misc/unison.ini [LDAP] certdbpath parameter documented in the Oracle Calendar Server Reference Manual is obsolete in this version of the Oracle Calendar server.

5.3 Engine daemon memory requirements

The stated memory requirements for the calendar server Engine daemon are incorrect. Use the following values in your sizing calculations:

Table 2 Engine memory requirements
Platform Memory per Engine (MB)

Solaris

1.0

HP-UX

2.5

Linux

1.8

Oracle is a registered trademark, and Oracle9i is a trademark or registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.

Copyright © 1993, 2002, Oracle Corporation. All Rights Reserved.


Oracle
Copyright © 1993, 2002 Oracle Corporation.

All Rights Reserved.