1 Suite-Level Issues

This chapter summarizes release note issues that affect all components of Oracle Collaboration Suite versions 9.0.4.1 and Patch Set 1 (9.0.4.2). It contains the following sections:

What's New?
Installation Issues
Known Limitations and Workarounds
Documentation Errata
Known Bugs in 9.0.4.1
Known Bugs in 9.0.4.2

What's New?

Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) is now available. This patch contains many important bug fixes, as well as new product features. To get the patch, go to OracleMetalink at:

http://metalink.oracle.com

For information about the new features and bugs fixed in this patch, see the Oracle Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.0).

Installation Issues

This section describes the following installation issues for Oracle Collaboration Suite Release 2 (9.0.4.1):

Installing on SUSE Linux Enterprise Server 9 (SLES 9)
Installing on SUSE Linux Enterprise Server (SLES) 8
Installing on Red Hat Enterprise Linux 3
Installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on Red Hat Enterprise Linux 3 for AMD64
Installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on Red Hat Enterprise Linux 4.0 Systems
Installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on SuSE SLES8 for AMD64

Installing on SUSE Linux Enterprise Server 9 (SLES 9)

To install Oracle Collaboration Suite on SuSE Linux Enterprise Server 9, complete the following steps in this section in addition to the procedure described in the Oracle Collaboration Suite Installation and Configuration Guide.

Software Requirements for SLES 9

Table 1-1 lists the operating system requirements for SLES 9 and the commands to determine the version of each component. For the most up-to-date list of of supported Operating System specific software for Oracle Collaboration Suite, check OracleMetalink at:

http://metalink.oracle.com

You must register online before using OracleMetalink.

Table 1-1 Software Requirements

Component	Requirements	Command
Linux kernel version	Kernel 2.6.5-7.97	`$ uname -a`
glibc version	`glibc-2.3.3-98`	`$ rpm -q glibc`
Required operating system packages	`binutils-2.15.90.0.1.1-32`	`$ rpm -q` `package_name`
	`pdksh-5.2.14`
	`sysstat-5.0.1`
	`libstdc++-3.3.3-43`
	`gcc-3.3.3-43`
	`orarun-1.8-109`
	`gnome-libs 1.4.1.7-671.1`

If you need to install a particular package, download it and install it as follows:

# rpm -i package_name

Setting the Environment for SLES 9

Set the LD_ASSUME_KERNEL environment variable to specify 2.4.21:

For the Bourne, Bash, or Korn shell:

$ LD_ASSUME_KERNEL=2.4.21
$ export LD_ASSUME_KERNEL

For the C or tcsh shell:
```
$ setenv LD_ASSUME_KERNEL 2.4.21
```

Set the LD_PRELOAD environment variable to include /usr/lib/libInternalSymbols.so:

For the Bourne, Bash, or Korn shell:

$ LD_PRELOAD=/usr/lib/libInternalSymbols.so
$ export LD_PRELOAD

For the C or tcsh shell:

$ setenv LD_PRELOAD /usr/lib/libInternalSymbols.so

Additional Preinstallation Steps for SLES 9

Perform the following preinstallation steps:

If necessary, create the following symbolic link for the perl executable:
```
$ ln -sf /usr/bin/perl /usr/local/bin/perl
```
If necessary, create the following symbolic link for the fuser executable:
```
$ ln -sf /bin/fuser /sbin/fuser
```
Perform the following steps as the root user to reset the environment:
1. Enter the following commands:
```
$ cd /etc/profile.d
$ mv oracle.csh oracle.csh.bak
$ mv oracle.sh oracle.sh.bak
$ mv alljava.sh alljava.sh.bak
$ mv alljava.csh alljava.csh.bak
```
2. Open a text editor and comment out the following lines from the $HOME/.profile file:
```
. ./.oracle
```
3. Log out of the oracle account.
4. Log back in to the oracle account for the changes to take effect.
If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.
Create the correct compiler environment, as follows:
1. Install the gcc_old package.
  
  This installs GCC 2.95.3-175.2 version in the /opt/gcc295 directory.
  Note:
  You can get the gcc_old package from the SuSE Maintenance Web site:
  http://sdb.suse.de/en/psdb/html/49cf8a59749a910eabbcaabd33d048ad.html
2. Because some Oracle make files have hard coded paths to the /usr/bin/gcc directory, create the following symbolic links:
```
$ ln -s /opt/gcc295/bin/gcc /usr/bin/gcc
$ ln -s /opt/gcc295/bin/gcc /usr/bin/cc
```
Check the /etc/services file and make sure that the following port ranges are available:
- Ports 4031-4040 required for Oracle Internet Directory
- Ports 1810-1814 required for Oracle Enterprise Manager
- At least 5 ports free in the range 2400-2700 for Real-Time Collaboration
- Port 4000 for Webcache
- Port 1521 for TNS Listener
- Ports 25, 143,110,993.995 for Email
  
  Note:
  For a complete list of the ports used, refer to the Oracle Collaboration Suite Installation and Configuration Guide.
If necessary, remove entries from the /etc/services file and reboot the system.

Additional Installation Steps on SLES 9

The following sections describe the additional installation steps required when installing Oracle9iAS infrastructure, Oracle Collaboration Suite information storage, and Oracle Collaboration Suite middle tier on SLES 9.

Oracle9iAS Infrastructure

Complete the following steps:

Install JDK 1.3.1_10, as follows:
1. Download the JDK 1.3.1_10 stagehome. See Oracle Bug 3335292 for more information.
2. Start the installer from the Disk1 directory of the downloaded shiphome.
3. Set the Destination path as the Infrastructure Oracle home directory (for example /opt/oracle/infra).
4. Do not change the Source path.
5. Continue and complete the installation of JDK 1.3.1_10.
Start the Oracle Universal Installer again from the Disk1 directory of the downloaded JDK 1.3.1_10 shiphome:
1. Verify the Destination path (for example /opt/oracle/infra) is the same directory that you specified when installing JDK 1.3.1_10.
2. Modify the Source path to specify the /Disk1/stage/products.jar file.
The Installer returns an error reporting insufficient memory. To resolve this:
1. Click OK in the Installer error window.
2. Do not close the Installer window.
3. Apply the patch for Oracle Bug 3656396.
Complete the installation as described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-2 lists the errors that might occur during the relink phase of the installation.

Table 1-2 Relink Errors on SLES 9

Error How to Resolve This Error...

Error	How to Resolve This Error...
`ins_sqlplus.mk` relink error	Perform the following: Open another terminal window. Set the ORACLE_HOME environment variable. Set the PATH environment variable to include the `$ORACLE_HOME/bin` directory. Apply the patch for Oracle Bug 3159913. Click Retry in the Installation error window.
`ins_ctx.mk` relink error	Perform the following: Open another terminal window. Apply the patch for Oracle Bug 2037255, and use the 9.0.1 version of the patch. Executing the `make` command as described in the patch README fails. Ignore the failure. Modify line 14 of the `$ORACLE_HOME/ctx/lib/ins_ctx.mk` file to include `$(LINKLDLIBS)` to the link line, as follows: $(LINK) $(CTXHXOBJ) bug2037255.o $(INSO_LINK) $(LINKLDLIBS) Click Retry in the Installer error screen.

ins_sqlplus.mk relink error

Perform the following:

Open another terminal window.
Set the ORACLE_HOME environment variable.
Set the PATH environment variable to include the $ORACLE_HOME/bin directory.
Apply the patch for Oracle Bug 3159913.
Click Retry in the Installation error window.

ins_ctx.mk relink error

Perform the following:

Open another terminal window.
Apply the patch for Oracle Bug 2037255, and use the 9.0.1 version of the patch.

Executing the make command as described in the patch README fails. Ignore the failure.
Modify line 14 of the $ORACLE_HOME/ctx/lib/ins_ctx.mk file to include $(LINKLDLIBS) to the link line, as follows:
```
$(LINK) $(CTXHXOBJ)  bug2037255.o $(INSO_LINK) $(LINKLDLIBS)
```
Click Retry in the Installer error screen.

Oracle Collaboration Suite Information Storage

Complete the following steps:

Download the patch for Oracle Bug 3903504. This patch provides an updated oraparam.ini file to support SLES 9.

Start the Installer from Disk1, as follows:

$ cdrom_mount/runInstaller -paramFile path_to_local_oraparam.ini

For example:

$ cdrom_mount/runInstaller -paramFile /home/oracle/oraparam.ini

In the screen in which the error for insufficient memory appears, click Continue.
Complete the installation as described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-3 lists the errors that might occur during the relink phase of the installation.

Table 1-3 Relink Errors on SLES 9

Error	To Resolve this Error:
`ins_sqlplus.mk` relink error	Perform the following: Open a new terminal window. Set the ORACLE_HOME environment variable. Set the PATH environment variable to include the `$ORACLE_HOME/bin` and `/sbin` directories. Apply patch for Oracle Bug 3152145. Check the `README.txt` file in the patch for steps specific to Red Hat 3.0 Click Retry in the Installer error window.
`ins_oemagent.mk` relink error	Perform the following: Open a new terminal window. Set the ORACLE_HOME environment window. Set the PATH Environment variable to include the `$ORACLE_HOME` directory. Apply the patch for Oracle bug 3119415, using the 9.2.0.3 version of the patch. Click Retry in the Installer error screen.

Oracle Collaboration Suite Middle Tier

Complete the following steps:

Install JDK 1.3.1_10, as follows:
1. Download the JDK 1.3.1_10 stagehome. See Oracle Bug 3335292 for more information.
2. Start Oracle Universal Installer from the Disk1 directory of the downloaded shiphome.
3. Set the Destination Path as the Oracle home directory for the Infrastructure, for example, /opt/oracle/infra.
4. Do not change the Source path.
5. Continue and complete the installation of JDK 1.3.1_10.
Start Oracle Universal Installer again from the Disk1 directory of the downloaded JDK 1.3.1_10 shiphome, as follows:
1. Verify that the Destination path, for example, /opt/oracle/midtier, is the same directory that you chose when installing JDK 1.3.1_10.
2. Modify the Source Path to specify the /Disk1/stage/products.jar file.
The Installer returns an error reporting insufficient memory. To resolve this:
1. Click OK in the Installer error window.
2. Do not close the Installer window.
3. Apply the patch for Oracle Bug 3656396.

Complete the installation as described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-4 lists the error that might occur during the relink phase, and explains how to resolve it.

Table 1-4 Relink Errors on SLES 9

Error	To Resolve This Error...
`ins_sqlplus.mk` relink error	Perform the following: Open a new terminal window. Set the ORACLE_HOME environment variable. Set the PATH environment variable to include the `$ORACLE_HOME/bin` directory. Apply the patch for Oracle bug 3159913. Click Retry in the Installer error screen.

When prompted to run the root.sh script, apply the patch for Oracle Bug number 3711218 as the oracle user. This prevents the Webcache Configuration Assistant from failing.

Postinstallation Steps on SLES 9

Set the LD_ASSUME_KERNEL environment variable to specify 2.4.21:

For the Bourne, Bash, or Korn shell:

$ LD_ASSUME_KERNEL=2.4.21
$ export LD_ASSUME_KERNEL

For the C or tcsh shell:
```
$ setenv LD_ASSUME_KERNEL 2.4.21
```

Set the LD_PRELOAD environment variable to include /usr/lib/libInternalSymbols.so:

For the Bourne, Bash, or Korn shell:

$ LD_PRELOAD=/usr/lib/libInternalSymbols.so
$ export LD_PRELOAD

For the C or tcsh shell:

$ setenv LD_PRELOAD /usr/lib/libInternalSymbols.so

Installation of Patchset 1 (9.0.4.2) on SLES 9

After you have successfully installed and configured Oracle Collaboration Suite release 9.0.4.1, apply Patch Set 1 (9.0.4.2 ), as follows:

Set up the environment as described in Chapter1, "Setting the Environment for SLES 9".
Download the patch set from OracleMetalink, as described in Oracle Bug 3564610.
Copy the Disk1/install/linux/oraparam.ini file to the local file system and modify the file by changing the line containing Linux=redhat-2.1,UnitedLinux-1.0 to Linux=

Start the Installer from Disk1 as follows:

$ cdrom_mount/runInstaller -paramFile path_to_local_oraparam.ini

For example:

$ cdrom_mount/runInstaller -paramFile /home/oracle/oraparam.ini

Apply the patch set as described in the Oracle Collaboration Suite patch set Readme file.

Known Issues on SLES 9

The following known bugs exist on SLES 9.

Table 1-5 Known Issues on SLES 9

Bug Number	Description	Action
3795078	Memory usage chart is not displayed in the Enterprise Manager webpage.	Apply the patch for the bug to resolve the problem.
3798290	Starting WebCache via WebCache Admin fails.	Use Enterprise Manager Console or OPMN to manage the Webcache or, if you use Webcache Admin GUI, it succeeds and you can ignore the error.
3800837	Installation of OCS 9041 ifsca completed successfully but when accessing the iFS link in the Enterprise Manager page, an error appears for incorrect password. List of ifs components also not displayed in that page.	Apply the patch for the bug to resolve the problem.

Installing on SUSE Linux Enterprise Server (SLES) 8

To install Oracle Collaboration Suite on UnitedLinux 1.0, complete the following steps in addition to the procedure described in the Oracle Collaboration Suite Installation and Configuration Guide.

Additional Preinstallation Steps for UnitedLinux

Complete the following steps before attempting to install Oracle Collaboration Suite on UnitedLinux 1.0:

Verify that the hostname command returns the fully qualified host name as shown below:
```
$ hostname 
hostname.domainname
```
Create the correct compiler environment:
1. Install the gcc_old package. This installs GCC 2.95.3 in the /opt/gcc295 directory.
2. Create the following symbolic links, which are required because some Oracle make files have hard coded paths to the /usr/bin/gcc directory.
```
prompt> ln -s /opt/gcc295/bin/gcc /usr/bin/gcc
prompt> ln -s /opt/gcc295/bin/gcc /usr/bin/cc
```
If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.

Note:
If you are installing UnitedLinux on a clean system, Oracle recommends that you do not install any of the Java packages supplied with the UnitedLinux distribution.
Create the following symbolic link for the Perl executable:
```
$ ln -sf /usr/bin/perl /usr/local/bin/perl
```
If the orarun package orarun-1.8-18 is installed on the system, unset the following environment variables:
- ORACLE_HOME
- ORACLE_SID
- ORACLE_BASE
- ORA_NLS33
- TNS_ADMIN
- SDK_HOME
- JDK_HOME
- JRE_HOME
- JAVA_HOME
- JAVA_ROOT
- CLASSPATH
Make sure that five ports in the range 1025-49151 are available.

If necessary, remove entries from the /etc/services file and reboot the system. These five ports in the range 1025-49151 (inclusive) are required by the Real-Time Collaboration (RTC) component and the associated configuration assistants will fail if 5 ports are not available.

Additional Installation Steps for UnitedLinux

When installing Infrastructure or Oracle Collaboration Suite on UnitedLinux 1.0, an error appears during the relinking phase. Do not close the Installer window. Complete the following steps to resolve the error:

Open a new terminal window.
Edit the $ORACLE_HOME/lib/sysliblist file and add the following entry to the end of the line:
```
-lgcc -L/opt/gcc295/lib/gcc-lib/i486-suse-linux/2.95.3 
```
Run the following command:
```
prompt> $ORACLE_HOME/bin/genclntsh
```
Click Retry in the Installer window. The installation continues without displaying further errors.

Installing on Red Hat Enterprise Linux 3

To install Oracle Collaboration Suite on Red Hat Enterprise Linux 3, complete the following steps in addition to the procedure described in the Oracle Collaboration Suite Installation and Configuration Guide.

Software Requirements

Table 1-6 lists the operating system requirements for Red Hat Enterprise Linux 3, and the commands to determine the version of each component. For the most up-to-date list of supported Red Hat Enterprise Linux 3 specific software packages, (for example, kernel version or rpm packages), check OracleMetaLink at:

http://metalink.oracle.com

You must register online before using OracleMetaLink.

Table 1-6 Operating System Requirements

Component Requirements Command

Linux kernel version 2.4.21-4.EL $ uname -a

glibc version glibc2.3.2-95.3 $ rpm -q glibc

Required operating system patches

Component	Requirements	Command
Linux kernel version	2.4.21-4.EL	`$ uname -a`
glibc version	`glibc2.3.2-95.3`	`$ rpm -q glibc`
Required operating system patches	`setarch-1.3-1` `pdksh-5.2.14` `gnome-libs-1.4.1.2.90-34.1` `compat-glibc-7.x-2.2.4.32.5` `compat-db-4.0.14.5` `compat-gcc-7.3-2.96.122` `compat-gcc-c++-7.3-2.96.122` `compat-libstdc++-7.3-2.96.122` `compat-libstdc++-devel-7.3-2.96.122`	`$ rpm -qa`

setarch-1.3-1

pdksh-5.2.14

gnome-libs-1.4.1.2.90-34.1

compat-glibc-7.x-2.2.4.32.5

compat-db-4.0.14.5

compat-gcc-7.3-2.96.122

compat-gcc-c++-7.3-2.96.122

compat-libstdc++-7.3-2.96.122

compat-libstdc++-devel-7.3-2.96.122

$ rpm -qa

Setting the Environment

Perform the following additional tasks to set up the environment before you begin the installation:

As the root user, rename the /usr/bin/gcc and /usr/bin/g++ executables, as follows:

prompt> mv /usr/bin/gcc /usr/bin/gcc323
prompt> mv /usr/bin/g++ /usr/bin/g++323

As the root user, enter the following commands to create symbolic links:

prompt> ln -s /usr/bin/gcc296 /usr/bin/gcc
prompt> ln -s /usr/bin/g++296 /usr/bin/g++

Verify that the hostname command returns the fully qualified host name, as follows:
```
prompt> hostname
hostname.domainname
```
Unset the Java environment variables if any Java packages are installed on the system. For example, enter the following command to unset the JAVA_HOME environment variable:
```
prompt> unset JAVA_HOME
```
Unset any Oracle-related installation environment variables if they are set by default. To unset an environment variable, enter the following command:
```
prompt> unset VARIABLE_NAME
```
Set the LD_ASSUME_KERNEL environment variable to specify kernel version 2.4.19.

For the C shell:
```
% setenv LD_ASSUME_KERNEL 2.4.19
```
For the Bourne, Bash or Korn shell:
```
$ LD_ASSUME_KERNEL=2.4.19; export LD_ASSUME_KERNEL
```

Additional Preinstallation Steps

Before you begin the installation, perform the following additional preinstallation steps:

Open a new terminal window.
Log in as the root user.
Apply patch 3006854 to resolve the libcwait symbol issue before running the Oracle Universal Installer. This patch is available at:
```
http://metalink.oracle.com
```
You must register online before using OracleMetaLink. After logging in to OracleMetaLink, select Patches from the left-hand column.

Additional Installation Steps

Oracle9iAS Infrastructure

When installing Oracle9iAS infrastructure on Red Hat Enterprise Linux 3, complete the following steps:

Download JDK 1.3.1_10 using patch 3335292.
Start the installer from the Disk 1 directory where you downloaded the JDK 1.3.1_10 installation software.
Enter the name and full path of the Oracle9iAS Infrastructure Oracle home directory as the destination path (for example, /opt/oracle/infra).

Note:
Do not alter the source path.
Complete the JDK 1.3.1_10 installation.
Start the installer from the Disk 1 directory where you downloaded the JDK 1.3.1_10 installation software again.
Verify that the destination path is the directory that you chose when installing JDK 1.3.1_10 (for example, /opt/oracle/infra).
Select mount_point/stage/products.jar as the source path.
Complete the remaining installation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-7 lists the errors that might occur during the relink phase, and explains how to resolve them.

Oracle Collaboration Suite Information Storage

When installing Oracle Collaboration Suite information storage on Red Hat Enterprise Linux 3, complete the following steps:

Copy mount_point/install/linux/oraparam.ini from the first CD-ROM to the local file system.
Edit the oraparam.ini file to change the line Linux=redhat-2.1, UnitedLinux-1.0 to the following:
```
Linux=
```
Complete the remaining preinstallation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.
To start the installer from the first CD-ROM, use the following command:
```
cdrom_mount/runinstaller -paramFile path/to/local_oraparam.ini
```
Note:
Start the installer from the same terminal you used to set up the environment.

Table 1-7 lists the errors that might occur during the relink phase, and explains how to resolve them.

Oracle Collaboration Suite Middle Tier

When installing Oracle Collaboration Suite middle tier on Red Hat Enterprise Linux 3, complete the following steps:

Download JDK 1.3.1_10 using patch 3335292.
Start the installer from the Disk 1 directory where you downloaded the JDK 1.3.1_10 installation software.
Enter the name and full path of the Oracle Collaboration Suite middle tier Oracle home directory as the destination path. For example /opt/oracle/mtier.

Note:
Do not change the source path.
Complete the JDK 1.3.1_10 installation.
Start the installer from the Disk 1 directory where you downloaded the JDK 1.3.1_10 installation software again.
Verify that the destination path is the directory that you entered in step 3.
Select mount_point/stage/products.jar as the source path.
Complete the remaining installation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-7 lists the errors that might occur during the relink phase, and explains how to resolve them.

Table 1-7 Relink Errors on Red Hat Enterprise Linux 3

Error	To Resolve This Error...
`ins_sqlplus.mk` relink error (Oracle9iAS infrastructure and Oracle Collaboration Suite middle tier)	Open a new terminal window. Set the ORACLE_HOME environment variable. Set PATH to include `$ORACLE_HOME/bin`. Apply patch 3159913. Click Retry in the OUI error window.
`ins_ctx.mk` relink error	Open a new terminal window. Apply patch 2037255 (version 9.0.1). Executing the `make` command, as described in the README.txt file in the patch, will fail. Ignore the failure. Edit the file `$ORACLE_HOME/ctx/lib/ins_ctx.mk` to include `$(LINKLDLIBS)` to the link line as follows: Line 14: $(LINK)$ (CTXHXOBJ) bug3027255.o $(INSO_LINK) $(LINKLDLIBS) Click Retry in the OUI error window.
`ins_sqlplus.mk` relink error (Oracle Collaboration Suite information storage)	Open a new terminal window. Set the ORACLE_HOME environment variable. Set PATH to include the following: $ORACLE_HOME/bin /sbin Apply patch 3152145. See the `README.txt` file in the patch for steps specific to Red Hat Enterprise Linux 3. Click Retry in the OUI error window.
oemagent relinking error in `ins_oemagent.mk`	Open a new terminal window. Set the ORACLE_HOME environment variable. Set the PATH environment variable to include `$ORACLE_HOME/bin`. Apply patch 3119415 (version 9.2.0.3). Click Retry in the OUI error window.

Additional Post-Installation Steps

Set the LD_ASSUME_KERNEL environment variable to specify kernel version 2.4.19.

For the C shell:

% setenv LD_ASSUME_KERNEL 2.4.19

For the Bourne, Bash or Korn shell:

$ LD_ASSUME_KERNEL=2.4.19; export LD_ASSUME_KERNEL

Known Issues and Bugs

This section describes the following known limitations and bugs when installing Oracle Collaboration Suite on Red Hat Enterprise Linux 3:

An incorrectly built binary error occurs when you perform the following tasks:
1. Start Webcache using the webcachectl start command.
2. Start and stop Calendar servers using the unistart and unistop commands.
The error text is as follows:

"Incorrectly built binary which accesses errno or h_errno directly. Needs to be fixed"

You can ignore this error.

The following known bug exists with Red Hat Enterprise Linux 3:

Bug #	Description	Action
3339835	Oracle Directory Manager (ODM) help navigator does not work properly. When you are installing Oracle9iAS infrastructure on Red Hat Enterprise Linux 3, the ODM help navigator does not display the table of contents of the help topics.	None

Installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on Red Hat Enterprise Linux 3 for AMD64

To install Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on Red Hat Enterprise Linux 3 for AMD64, complete the following steps for installing Oracle Collaboration Suite Release 2 (9.0.4.1.0) in addition to the procedure described in the Oracle Collaboration Suite Installation and Configuration Guide. Then complete the final steps for installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0).

Software Requirements

Complete the following additional steps before installing Oracle Collaboration Suite Release 2 (9.0.4.1.0):

Log in as the root user.
Verify that Red Hat Enterprise Linux AS/ES 3.0 and Quarterly Update 1 are installed, using the following command:
```
prompt> cat/etc/issue
Red Hat Enterprise Linux AS release 3 (Taroon Update 1)
```

Check that the minimum supported kernel, glibc version, and required software packages are installed.

Table 1-8 lists the operating system requirements for Red Hat Enterprise Linux 3 for AMD64, and the commands to determine the version of each component. For the most up-to-date list of supported Red Hat Enterprise Linux 3 for AMD64 specific software packages, (for example, JDK version), check OracleMetaLink at:

http://metalink.oracle.com

You must register online before using OracleMetaLink.

To determine if a package is installed, enter a command similar to the following:

prompt> rpm -q package_name

If a package is missing, download and install it using a command similar to the following:

prompt> rpm -i package_name

Table 1-8 Operating System Requirements

Component Requirements Command

Linux kernel version 2.4.21-9.EL prompt> uname -a

glibc version glibc2.3.2-95.6 prompt> rpm -q glibc

Required operating system patches

Component	Requirements	Command
Linux kernel version	2.4.21-9.EL	`prompt> uname -a`
glibc version	`glibc2.3.2-95.6`	`prompt> rpm -q glibc`
Required operating system patches	`gcc-3.2.3-20.x86_64` `libgcc-3.2.3-20.i386` `setarch-1.3-1.x86_64` `pdksh-5.2.14-21.x86_64` `compat-glibc-7.x-2.2.4.32.5.i386`^{Foot 1} `compat-gcc-7.3-2.96.122.i386` `compat-libstdc++-7.3-2.96.122.i386` `compat-libstdc++-devel-7.3-2.96.122.i386` `compat-gcc-c++-7.3-2.96.122.i386` `sysstat-4.0.7-4.x86_64` `gnome-libs-1.4.1.2.90-34.1.i386`¹	`prompt> rpm -qa`

gcc-3.2.3-20.x86_64

libgcc-3.2.3-20.i386

setarch-1.3-1.x86_64

pdksh-5.2.14-21.x86_64

compat-glibc-7.x-2.2.4.32.5.i386^{Foot 1}

compat-gcc-7.3-2.96.122.i386

compat-libstdc++-7.3-2.96.122.i386

compat-libstdc++-devel-7.3-2.96.122.i386

compat-gcc-c++-7.3-2.96.122.i386

sysstat-4.0.7-4.x86_64

gnome-libs-1.4.1.2.90-34.1.i386¹

prompt> rpm -qa

^{Footnote 1} Red Hat Enterprise Linux 3 for x86

Additional Preinstallation Steps

Perform the following additional preinstallation steps before you begin the installation:

Open a new terminal window.
Log in as the root user.
Apply patch 3423540. This patch creates the /stub/lib/libcwait.so library (32-bit shared library) and /stub/lib64/libcwait.so library (64-bit shared library). Then append the following line to the /etc/ld.so.preload file:
```
/stub/$LIB/libcwait.so
```
This patch is available at:
```
http://metalink.oracle.com
```
You must register online before using OracleMetaLink. After logging in to OracleMetaLink, select Patches from the left-hand column.

Note:
As installation of this patch requires the gcc-3.2.3-20 (x86-64) executables in the /usr/bin/gcc directory, you must apply the patch before proceeding to the following step.

Setting the Environment

Perform the following additional tasks to set up the environment before you begin the installation:

Log in as the root user.
Ensure that the following symbolic links for the compiler environment exist:
```
gcc -> gcc296g++ -> g++296
```
To verify if the symbolic links exist, use the following commands:
```
prompt> cd /usr/bin
prompt> ls -l gcc g++
```
If the symbolic links do not exist, you must create them. As the root user, perform the following:
1. Create a backup of existing files, using the following commands:
```
prompt> mv /usr/bin/gcc /usr/bin/gcc.backupprompt> mv /usr/bin/g++ /usr/bin/g++.backup
```
2. Create the symbolic links for the compiler environment, using the following commands:
```
prompt> ln -s /usr/bin/gcc296 /usr/bin/gccprompt> ln -s /usr/bin/g++296 /usr/bin/g++
```
You can restore the original files if required, however you must recreate the links as described in this procedure for Oracle Collaboration Suite installations to relink properly.
If the hugemem kernel is used, set the architecture using the following command:
```
prompt> setarch i386
```
Verify that the hostname command returns the fully qualified host name, as follows:
```
prompt> hostname   
hostname.domainname 
```
Log in as the oracle user.
Unset any Oracle-related installation environment variables if they are set by default. For example, unset ORACLE_HOME, PATH, LD_LIBRARY_PATH in the .profile or .login files or scripts in /etc/profile.d. To unset an environment variable, enter the following command:
```
prompt> unset VARIABLE_NAME
```
Unset the Java environment variables if any Java packages are installed on the system. For example, enter the following command to unset the JAVA_HOME environment variable:
```
prompt> unset JAVA_HOME
```

Set the following environment variables:

For the C shell:

% setenv LDEMULATION elf_i386
% setenv LD_ASSUME_KERNEL 2.4.19

For the Bourne, Bash or Korn shell:

$ LDEMULATION=elf_i386; export LDEMULATION
$ LD_ASSUME_KERNEL=2.4.19; export LD_ASSUME_KERNEL

Use the linux32 emulator before installing Oracle Collaboration Suite 9.0.4.1.0 or running any Oracle Collaboration Suite 9.0.4.1.0 processes from a working shell. The command to start the linux32 emulator is as follows:
```
prompt> linux32 bash
```

Additional Installation Steps

Oracle9iAS Infrastructure

When installing Oracle9iAS infrastructure on Red Hat Enterprise Linux 3 for AMD64, complete the following steps:

Download the JDK 131_10 installation software using patch 3335292.
Extract the downloaded installation software into a temporary area.
Start the installer from the Disk1 directory in the temporary area.
Enter the name and full path of the Oracle9iAS Infrastructure Oracle home directory as the destination path (for example /opt/oracle/infra).

Note:
Do not alter the source path.
Complete the JDK 1.3.1_10 installation.
Start the installer again from the Disk1 directory where you downloaded the JDK 1.3.1_10 installation software.
Verify that the destination path is the same directory that you chose when installing JDK 1.3.1_10 (for example /opt/oracle/infra).
Select disk1_mount_point/stage/products.jar as the source path.
Complete the remaining installation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-9 lists the errors that might occur during the relink phase and explains how to resolve them.

Oracle Collaboration Suite Information Storage

When installing Oracle Collaboration Suite information storage on Red Hat Enterprise Linux 3 for AMD64, complete the following steps:

Copy the disk1_mount_point/install/linux/oraparam.ini file to the local file system.
Edit the oraparam.ini file by changing the following line:
```
Linux=redhat-2.1, UnitedLinux-1.0
```
to:
```
Linux=
```
Complete the remaining preinstallation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.
To start the installer from Disk1, use the following command, where parameterfile is the location of the oraparam.ini file (for example /home/oracle/oraparam.ini):
```
disk1_mount_point/runinstaller -paramFile parameterfile
```
Note:
Start the installer from the same terminal you used to set up the environment.

Table 1-9 lists the errors that might occur during the relink phase, and explains how to resolve them.

Oracle Collaboration Suite Middle Tier

When installing Oracle Collaboration Suite middle tier on Red Hat Enterprise Linux 3 for AMD64, complete the following steps:

Download the JDK 131_10 installation software using patch 3335292.
Extract the downloaded installation software into a temporary area.
Start the installer from the Disk1 directory in the temporary area.
Enter the name and full path of the Oracle Collaboration Suite middle tier Oracle home directory as the destination path (for example, /opt/oracle/mtier).

Note:
Do not alter the source path.
Complete the JDK 1.3.1_10 installation.
Start the installer again from the Disk1 directory where you downloaded the JDK 1.3.1_10 installation software.
Verify that the destination path is the same directory that you chose when installing JDK 1.3.1_10 (for example, /opt/oracle/mtier).
Select disk1_mount_point/stage/products.jar as the source path.
Complete the remaining installation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-9 lists the errors that might occur during the relink phase, and explains how to resolve them.

Table 1-9 Relink Errors on Red Hat Enterprise Linux 3 for AMD64

Error	To Resolve This Error...
`ins_sqlplus.mk` relink error (Oracle9iAS infrastructure and Oracle Collaboration Suite middle tier)	Open a new terminal window. Set the ORACLE_HOME environment variable. Set the PATH environment variable to include `$ORACLE_HOME/bin`. Apply patch 3159913. Click Retry in the OUI error window.
`ins_ctx.mk` relink error	Open a new terminal window. Apply patch 2037255 (version 9.0.1). Executing the `make` command, as described in the `README.txt` file in the patch, fails. Ignore the failure. Edit the `$ORACLE_HOME/ctx/lib/ins_ctx.mk` file to include $(LINKLDLIBS) to the link line as follows: Line 14: $(LINK)$ (CTXHXOBJ) bug3027255.o $(INSO_LINK) $(LINKLDLIBS) Click Retry in the OUI error window.
`ins_sqlplus.mk` relink error (Oracle Collaboration Suite information storage)	Open a new terminal window. Set the ORACLE_HOME environment variable. Set the PATH environment variable to include the following: $ORACLE_HOME/bin /sbin Apply patch 3152145. See the `README.txt` file in the patch for steps specific to Red Hat Enterprise Linux 3. Click Retry in the OUI error window.
oemagent relinking error in `ins_oemagent.mk`	Open a new terminal window. Set the ORACLE_HOME environment variable. Set the PATH environment variable to include `$ORACLE_HOME/bin`. Apply patch 3119415 (version 9.2.0.3). Click Retry in the OUI error window.

Installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0)

After performing the required preinstallation, installation, and configuration tasks for Oracle Collaboration Suite Release 2 (9.0.4.1.0) on Red Hat Enterprise Linux 3 for AMD64, apply the Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0), as follows:

Verify that the environment is set up according to the instructions in Chapter1.
Download the patch set from OracleMetalink using Bug 3564610.
Install the patch set on the Oracle9iAS infrastructure, Oracle Collaboration Suite information storage, and Oracle Collaboration Suite middle tier areas using the instructions in the Oracle Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.0).

Setting the Runtime Environment

Perform the following tasks to set up the runtime environment before running Oracle Collaboration Suite 9.0.4.1.0 processes:

Set the following environment variables:

For the C shell:

% setenv LDEMULATION elf_i386
% setenv LD_ASSUME_KERNEL 2.4.19

For the Bourne, Bash or Korn shell:

$ LDEMULATION=elf_i386; export LDEMULATION
$ LD_ASSUME_KERNEL=2.4.19; export LD_ASSUME_KERNEL

Use the linux32 emulator running any Oracle Collaboration Suite 9.0.4.1.0 processes from a working shell. Start the linux32 emulator as follows:
```
prompt> linux32 bash
```

Installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on Red Hat Enterprise Linux 4.0 Systems

To install Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on Red Hat Enterprise Linux 4.0, complete the following steps for installing Oracle Collaboration Suite Release 2 (9.0.4.1.0) in addition to the procedure described in the Oracle Collaboration Suite Installation and Configuration Guide. Then complete the final steps for installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0).

Software Requirements

Oracle Collaboration Suite (9.0.4.2) is certified with the following Red Hat Enterprise Linux 4.0 packages. For the most current list of supported Red Hat Enterprise Linux 4.0 specific software packages, (for example kernel version, rpm packages) check OracleMetaLink: http://metalink.oracle.com

You must register online before using OracleMetaLink.

Table 1-10 lists the operating requirements.

Table 1-10 Operating System Requirements

Component	Requirement	Command
Linux kernel version	`kernel-smp-2.6.9-5.EL`	`prompt> uname -a`
Required Operating System packages	`gcc-3.4.3-9.EL4`	`prompt> rpm -qa`
	`gcc-c++-3.4.3-9.EL4`
	`libgcc-3.4.3-9.EL4`
	`glibc-2.3.4-2`
	`compat-db-4.1.25-9`
	`compat-libgcc-296-2.96-132.7.2`
	`compat-libstdc++-296-2.96-132.7.2`
	`compat-libgcc-296-2.96-132.7.2`
	`compat-gcc-32-3.2.3-47.3`
	`compat-gcc-32-c++-3.2.3-47.3`
	`compat-oracle-rhel4-1.0-3` You can get this from OracleMetalink: `http://metalink.oracle.com`
	`compat-libcwait-2.0.1` You can get this from OracleMetalink: `http://metalink.oracle.com`
	`gnome-libs-1.4.1.2.90-44.1`
	`pdksh-5.2.14-30`
	`binutils-2.15.92.0.2-10.EL4`

Setting the Environment

Perform the following additional tasks to set up the environment before you begin the installation:

Verify that the hostname command returns the fully qualified host name as shown below:
```
$ hostname 
hostname.domainname
```
If any Java packages are installed on the system, unset the Java environment variables, for example JAVA_HOME.
Unset any Oracle-related installation environment variables if they are set by default. For example, unset ORACLE_HOME, PATH, LD_LIBRARY_PATH in the .profile or .login files or scripts in /etc/profile.d. To unset an environment variable, enter the following command:
```
prompt> unset VARIABLE_NAME
```
Set the LD_ASSUME_KERNEL environment variable to specify kernel version 2.4.19.

For the C shell:
```
% setenv LD_ASSUME_KERNEL 2.4.19
```
For the Bourne, Bash or Korn shell:
```
$ LD_ASSUME_KERNEL=2.4.19; export LD_ASSUME_KERNEL
```

Additional Installation Steps

Oracle9iAS Infrastructure

When installing Oracle9iAS infrastructure on Red Hat Enterprise Linux 4.0, complete the following steps:

Complete the environment set up as described at the start of this section.
Install JDK 1.3.1_10, as follows:
1. Download the JDK 131_10 installation software using patch 3335292.
2. Start the installer from the Disk1 directory of the downloaded shiphome.
3. Enter the name and full path of the Oracle9iAS Infrastructure Oracle home directory as the destination path (for example /opt/oracle/infra).
4. Do not change the Source Path.
5. Continue and complete the installation of the JDK.
Start the installer again from the Disk1 directory of the downloaded JDK 131_10 shiphome.
Verify the Destination Path, for example /opt/oracle/infra, is the same as the one you specified when installing the JDK.
Modify the Source Path to select Infrastructure_CD/DIsk1/stage/products.jar
Continue the installation by following the instructions described in the Oracle Collaboration Suite Installation and Configuration Guide.
The installer returns an error reporting insufficient memory. To resolve this problem:
1. Select the installer error window and do not close it.
2. Apply the patch for Oracle bug 3656396.
3. Continue the installation.
Continue and complete the installation.
Table 1-9 lists the errors that might occur during the relink phase, and explains how to resolve them.

Oracle Collaboration Suite Information Storage

When installing Oracle Collaboration Suite information storage, complete the following steps:

Complete the environment setup as described at the start of this section.
Download the JDK 131_10 installation software using patch 3335292.
Start the installer from the Disk1 directory of the downloaded shiphome.
Modify the Source Path to select Information_Storage_CD/Disk1/stage/products.jar.
Continue the installation by following the instructions described in the Oracle Collaboration Suite Installation and Configuration Guide.
The installer returns an error reporting insufficient memory. To resolve this:
1. Click on the installer error window and do not close the window.
2. Apply the patch for Oracle bug 3656396.
3. Continue the installation.
Complete the remaining tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.
Table 1-9 lists the errors that might occur during the relink phase, and explains how to resolve them.
Continue and complete the installation.

Oracle Collaboration Suite Middle Tier

When installing Oracle Collaboration Suite middle tier on Red Hat Enterprise Linux 4.0, complete the following steps:

Complete the environment setup as described at the start of this section.
Install JDK 1.3.1_10, as follows:
1. Download JDK 131_10 shiphome using Oracle bug 3335292.
2. Start the installer from the Disk1 directory of the downloaded shiphome.
3. Enter the name and full path of the Oracle Collaboration Suite middle tier Oracle home directory as the destination path (for example, /opt/oracle/mtier).
4. Do not change the Source Path.
5. Continue and complete the installation of JDK 131_10.
Start the installer again from the Disk1 directory where you downloaded the JDK 1.3.1_10 installation software.
Verify that the destination path is the same directory that you chose when installing JDK 1.3.1_10 (for example, /opt/oracle/mtier)
Modify Source Path to select Middletier_CD/Disk1/stage/products.jar.
Complete the remaining installation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.
The installer returns an error reporting insufficient memory. To resolve this error:
1. Click on the installer error window and do not close the window.
2. Apply the patch for Oracle bug 3656396.
3. Continue the installation.

Table 1-9 lists the errors that might occur during the relink phase, and explains how to resolve them.

Known Issues

The 'Incorrectly built binary which accesses errno or h_errno directly. Needs to be fixed' error is displayed in the terminal window when:

starting Webcache using the webcachectl start command
starting and stopping Calendar servers using unistart and unistop.

You can ignore these errors.

The issues listed in Table 1-5 apply to Red Hat Enterprise Linux 4.0 also.

Postinstallation Step for Wireless EMD Integration

When you install OCS 9.0.4.1.0 on Red Hat Enterprise Linux 4.0, the wireless schema username and passwords are not instantiated in the targets.xml file.

Perform the following workaround to correct this:

Create a backup of the $ORACLE_HOME/sysman/emd/targets.xml file.

Open the $ORACLE_HOME/sysman/emd/targets.xml file and change the following lines in the oracle_wireless target xml segment to look like the following:

<Property NAME="UserName" VALUE="wireless" ENCRYPTED="FALSE"/>
<Property NAME="password" VALUE="WIRELESS_SCHEMA_PASSWORD" ENCRYPTED="FALSE"/>
<Property NAME="ConfigDBUserName" VALUE="wireless" ENCRYPTED="FALSE"/>
<Property NAME="ConfigDBpassword" VALUE="WIRELESS_SCHEMA_PASSWORD"
ENCRYPTED="FALSE"/>

where WIRELESS_SCHEMA_PASSWORD is the wireless schema password.

Save the targets.xml file and restart the EMD server.

Installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on SuSE SLES8 for AMD64

To install Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0) on Suse SLES 8 for AMD64, complete the following steps for installing Oracle Collaboration Suite Release 2 (9.0.4.1.0) in addition to the procedure described in the Oracle Collaboration Suite Installation and Configuration Guide. Then complete the final steps for installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0).

Software Requirements

Complete the following additional steps before installing Oracle Collaboration Suite Release 2 (9.0.4.1.0):

Log in as the root user.
Verify if SLES 8 has been updated to at least Service Pack 3. For example, check if the /etc/UnitedLinux-release file contains the following line:
```
PATCH_LEVEL = 3
```
If not, update SLES 8 to Service Pack 3. Note that Service Pack 3 does not include all the packages in Service Pack 2. You must install Service Pack 2 before installing Service Pack 3.
Deinstall the following packages. To verify if a package is installed, use the following command:
```
prompt> rpm -qa
```
- gcc
- gcc-c++
- evlog
- kernel-source
- binutils
- qt3-devel
- arts-devel
- kdelibs3-devel
- kdenetwork3-devel
- kdebase3-devel
Install the following 32-bit libraries required for relinking the Oracle database binaries and libraries. Be sure to install the packages from the Service Pack 2 distribution. Note that some of the packages might have been installed previously.
- UnitedLinux/i586/glibc-32bit-8.1-10.i586.rpm
- UnitedLinux/i586/baselibs-32bit-8.1-10.i586.rpm
- UnitedLinux/i586/devel_libs-32bit-8.1-10.i586.rpm
- UnitedLinux/i586/glibc-devel-32bit-8.1-10.i586.rpm
Install the following packages with the --nodeps option. For example:
```
prompt> rpm -i gcc_old-2.95.3-78.i586.rpm --nodeps
```
- orarun-1.8-29.i586.rpm
  
  Note:
  The orarun package does not need to be installed if the oracle user is configured manually.
- gcc_old-2.95.3-78.i586.rpm
- binutils-2.12.90.0.15-75.i586.rpm

Check that the minimum supported kernel, glibc version, and required software packages are installed.

Table 1-8 lists the operating system requirements for SuSE SLES8 for AMD64, and the commands to determine the version of each component. For the most up-to-date list of supported SuSE SLES8 for AMD64 specific software packages, (for example, JDK version), check OracleMetaLink at:

http://metalink.oracle.com

You must register online before using OracleMetaLink.

To determine if a package is installed, enter a command similar to the following:

prompt> rpm -q package_name

If a package is missing, download and install it using a command similar to the following:

prompt> rpm -i package_name

Table 1-11 Operating System Requirements

Component Requirements Command

Linux kernel version 2.4.21 prompt> uname -a

glibc version glibc2.2.5-213 prompt> rpm -q glibc

Required operating system patches

Component	Requirements	Command
Linux kernel version	2.4.21	`prompt> uname -a`
glibc version	`glibc2.2.5-213`	`prompt> rpm -q glibc`
Required operating system patches	`pdksh-5.2.14` `sysstat-4.0.3` `libstdc++-3.2.2-38` `glibc-32bit-8.1-10` `baselibs-32bit-8.1-10` `devel_libs-32bit-8.1-10` `glibc-devel-32bit-8.1-10` `orarun-1.8-29` `gcc_old-2.95.3-78` `binutils-2.12.90.0.15-75`	`prompt> rpm -qa`

pdksh-5.2.14

sysstat-4.0.3

libstdc++-3.2.2-38

glibc-32bit-8.1-10

baselibs-32bit-8.1-10

devel_libs-32bit-8.1-10

glibc-devel-32bit-8.1-10

orarun-1.8-29

gcc_old-2.95.3-78

binutils-2.12.90.0.15-75

prompt> rpm -qa

Setting the Environment

Perform the following additional tasks to set up the environment before you begin the installation:

Verify whether the following symbolic link exists for the perl executable:
```
prompt> ls -l /usr/local/bin/perl
```
Create the following symbolic link for the perl executable if it does not already exist:
```
prompt> ln -sf /usr/bin/perl /usr/local/bin/perl
```
Verify whether the following symbolic link exists for the fuser executable:
```
prompt> ls -l /sbin/fuser
```
Create the following symbolic link for the fuser executable if it does not already exist:
```
prompt> ln -sf /bin/fuser /sbin/fuser
```
Ensure that the following symbolic links for the compiler environment exist:
```
gcc -> /opt/gcc295/bin/gcccc -> /opt/gcc295/bin/gcc
```
To verify whether the symbolic links exist, use the following commands:
```
prompt> cd /usr/bin
prompt> ls -l gcc cc
```
If the symbolic links do not exist, you will need to create them. As the root user, perform the following tasks:
1. Create a backup of existing files, using the following commands:
```
prompt> mv /usr/bin/gcc /usr/bin/gcc.backupprompt> mv /usr/bin/cc /usr/bin/cc.backup
```
2. Create the symbolic links for the compiler environment, using the following commands:
```
prompt> ln -s /opt/gcc295/bin/gcc /usr/bin/gccprompt> ln -s /opt/gcc295/bin/gcc /usr/bin/cc
```
You can restore the original files if required, however you must recreate the links as described in this procedure for Oracle Collaboration Suite installations to relink properly.
Verify if the following symbolic link exists:
```
prompt> ls -l /lib/libgcc.a
```
Create the following symbolic link if it does not already exist:
```
prompt> ln -s /opt/gcc295/lib/gcc-lib/i486-suse-linux/2.95.3/libgcc.a /lib/libgcc.a
```
Note:
Depending on the Linux distribution, the first path in the previous command might contain a string other than suse.
If the orarun package was installed, complete the following steps as the oracle user to reset the environment:
1. Enter the following commands:
```
prompt> cd /etc/profile.d
prompt> mv oracle.csh oracle.csh.bak
prompt> mv oracle.sh oracle.sh.bak
prompt> mv alljava.sh alljava.sh.bak
prompt> mv alljava.csh alljava.csh.bak
```
2. Use any text editor to comment out the following line from the $ORACLE_HOME/.profile file:
```
.  ./.oracle
```
3. Log out of the oracle user account.
4. Log in to the oracle user account for the changes to take effect.
Check the /etc/services file to make sure that the following port ranges are available:
- Ports 4031-4040 for the Oracle Internet Directory
- Port 1810 for Oracle Enterprise Manager
- At least five ports free in the range 2400-2700 for Real-Time Collaboration
  
  If necessary, remove entries from the /etc/services file and reboot the system. If the above ports are not available, the associated configuration assistants will fail during installation.
If you use Network Information Service (NIS), perform the following tasks:
1. Make sure that the following line exists in the /etc/yp.conf file:
```
hostname.domainname broadcast
```
2. Make sure that the following line exists in the /etc/nsswitch.conf file:
```
hosts: files nis dns
```
Unset the Java environment variables if any Java packages are installed on the system. For example, enter the following command to unset the JAVA_HOME environment variable:
```
prompt> unset JAVA_HOME
```
Use the linux32 emulator before installing Oracle Collaboration Suite 9.0.4.1.0 or running any Oracle Collaboration Suite 9.0.4.1.0 processes from a working shell. The command to start the linux32 emulator is as follows:
```
prompt> linux32 bash
```

Additional Installation Steps

Oracle9iAS Infrastructure

When installing Oracle9iAS infrastructure on SuSE SLES8 for AMD64, complete the following steps:

Download the JDK 131_10 installation software using patch 3335292.
Extract the downloaded installation software into a temporary area.
Start the installer from the Disk1 directory in the temporary area.
Enter the name and full path of the Oracle9iAS Infrastructure Oracle home directory as the destination path (for example, /opt/oracle/infra).

Note:
Do not alter the source path.
Complete the JDK 1.3.1_10 installation.
Start the installer again from the Disk1 directory where you downloaded the JDK 1.3.1_10 installation software.
Verify that the destination path is the same directory that you chose when installing JDK 1.3.1_10 (for example, /opt/oracle/infra).
Select disk1_mount_point/stage/products.jar as the source path.
Complete the remaining installation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-12 lists the errors that might occur during the relink phase, and explains how to resolve them.

Oracle Collaboration Suite Information Storage

After performing the required pre-installation tasks, install Oracle Collaboration Suite information storage on Suse SLES8 for AMD64 following the procedure in the Oracle Collaboration Suite Installation and Configuration Guide.

Oracle Collaboration Suite Middle Tier

When installing Oracle Collaboration Suite middle tier on Suse SLES8 for AMD64, complete the following steps:

Download the JDK 131_10 installation software using patch 3335292.
Extract the downloaded installation software into a temporary area.
Start the installer from the Disk1 directory in the temporary area.
Enter the name and full path of the Oracle Collaboration Suite middle tier Oracle home directory as the destination path (for example, /opt/oracle/mtier).

Note:
Do not alter the source path.
Complete the JDK 1.3.1_10 installation.
Start the installer again from the Disk1 directory where you downloaded the JDK 1.3.1_10 installation software.
Verify that the destination path is the same directory that you chose when installing JDK 1.3.1_10 (for example, /opt/oracle/mtier).
Select disk1_mount_point/stage/products.jar as the source path.
Complete the remaining installation tasks described in the Oracle Collaboration Suite Installation and Configuration Guide.

Table 1-12 lists an error that might occur during the relink phase, and explains how to resolve it.

Table 1-12 Relink Errors on SuSE SLES8 for AMD64

Error	To Resolve This Error...
`ins_sqlplus.mk` relink error (Oracle9iAS infrastructure and Oracle Collaboration Suite middle tier)	Open a new terminal window. Set the ORACLE_HOME environment variable. Set PATH to include `$ORACLE_HOME/bin`. Modify `$ORACLE_HOME/bin/genclntsh` by commenting out the line containing LD_SELF_CONTAINED. Execute `$ORACLE_HOME/bin/genclntsh`. Click Retry in the OUI error window.

Installing Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0)

After performing the required preinstallation, installation, and configuration tasks for Oracle Collaboration Suite Release 2 (9.0.4.1.0) on Suse SLES8 for AMD64, apply the Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.0), as follows:

Verify that the environment is set up according to the instructions in Chapter1.
Download the patch set from OracleMetalink using Bug 3564610.
Install the patch set on the Oracle9iAS infrastructure, Oracle Collaboration Suite information storage, and Oracle Collaboration Suite middle tier areas using the instructions in the Oracle Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.0).

Known Limitations and Workarounds

This section describes the following known limitations and workarounds for Oracle Collaboration Suite Release 2 (9.0.4.1).

Cannot Enable RAC with a Pre-seeded Information Storage Database
Errors Occur in Oracle Collaboration Suite if Portal is Not Installed
Oracle Collaboration Suite Web Client
Oracle Enterprise Manager for Oracle Email Not Invoked
Referenced Name Error Occurs During Email Upgrade
Database is Not Being Registered
Database Configuration Assistant Error
Single Sign-On Photograph Registration
Create or Edit User Information in Delegated Administration Service
File Not Found Error Occurs During Execution of the root.sh Script
Welcome Page iSupport Link
Port Number Changes When Upgrade Assistant is Executed
Configure Oracle Collaboration Suite Components with SSL
Linux Only: Upgrading Oracle Calendar
Linux Only: Oracle Enterprise Manager Process Running Query Check Might Hang
HP-UX Only: Pre-Requisite Failure in 11.0 System When Using $ORACLE_HOME/oui/bin/runinstaller

Cannot Enable RAC with a Pre-seeded Information Storage Database

Currently, Oracle Real Application Clusters (RAC) cannot be enabled with a pre-seeded Oracle Collaboration Suite Release 2 information storage database.

Workaround:

Install a 9.2.0.1 custom RAC enabled database from the Oracle9i Release 2 (9.2.0.1) database CD-ROM and apply the 9.2.0.3 patch set.

See Also:

Bug 3098122 for more information about this issue.

Errors Occur in Oracle Collaboration Suite if Portal is Not Installed

During the Oracle Collaboration Suite middle tier installation, the Oracle Universal Installer (OUI) lets you decide whether or not to configure Portal. While Portal is an optional component of Oracle Collaboration Suite, failure to configure Portal on at least one middle tier results in some broken links in the Web client. For example, an error occurs if you:

Click Log on to Oracle Collaboration Suite in the "End-User Login" section of the default welcome page (index.html).
Click the Return to Portal global link in web applications, such as Oracle Email and Oracle Files.

Oracle recommends that you configure Portal on at least one Oracle Collaboration Suite middle tier. Portal provides a convenient launch pad for accessing Oracle Collaboration Suite web applications.

Note:

Configuring Portal is a required prerequisite of configuring the Oracle Collaboration Suite Web client.

If you choose not to configure Portal as part of your installation, you can find the direct entry point URLs for various web applications, such as Oracle Email, Oracle Files, and Oracle Calendar in the following file:

$ORACLE_HOME/webclient/classes/oracle/ \ collabsuite/webclient/resources/webclient.properties

Oracle Collaboration Suite Web Client

This section describes Oracle Collaboration Suite Web Client issues.

Web Client might not Work on Korean Locale

The Web client might not work if you are using Internet Explorer on Korean Windows 2000.

The Web Client Configuration Assistant Fails in the Upgrade Scenario

Workaround: Manually invoke the Web client configuration assistant from the command line as described in the following procedure.

Before invoking the Web client configuration assistant, manually ensure that the Oracle9iAS Portal middle tier has been installed or upgraded, and configured.

Skip section 1.2.3.2.1, if the host name and port number for the applications were provided during the Web client installation through Oracle Universal Installer.

Configuring the Component URL

This section explains how to configure component URL such as Oracle Email, Oracle Files, and Oracle Calendar. You configure the component URL by modifying the webclient.properties file.

The webclient.properties file contains three URL for each Oracle Collaboration Suite component:

- Help page URL
- Application entry point URL
- Portlet provider URL

Open the webclient.properties file located in the $ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources directory.
In the webclient.properties file, set the entry point URL for each configured component.

Replace the token for the host name and the port number in all three URLs for each component to be configured.

If you are not upgrading Oracle Calendar to Release 2 (9.0.4.1), perform the following steps to make Oracle Calendar Release 1 (9.0.3) available as a portlet:
1. Open the webclient.properties file from the $ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources directory on the Oracle Collaboration Suite Release 2 (9.0.4.1) middle tier.
2. Locate the following statement:
  
  calendar=http://%CALENDAR_HOST%:%CALENDAR_PORT%/ocas-bin/ocas.fcgi?sub=web
  
  Change it to:
  
  calendar=http://%CALENDAR_HOST%:%CALENDAR_PORT%/fcgi-bin/owc/lexacal.fcgi?go=login
3. Locate the following statement:
  
  calendar.provider=http://%WEBCLIENT_HOST%:%WEBCLIENT_PORT%/webclient-calendar/servlet/soaprouter
  
  Change it to:
  
  calendar.provider= http://%WIRELESS_HOST%:%WIRELESS_PORT%/marconi/servlet/soaprouter

Running the Web Client Configuration Assistant from the Command-line

Enter the following command:

$ORACLE_HOME/webclient/bin/webclient_installer.sh Oradcle9iAS_Portal_user_name Oradcle9iAS_Portal_user_password -complete

If you know the Oracle9iAS Portal schema name, password, and connect string information, you can invoke the configuration assistant, as follows:

$ORACLE_HOME/webclient/bin/webclient_installer.sh Oracle9iAS_Portal_user_name Oracle9iAS_Portal_user_password -complete -s
schema -p password -c connect_string

Where:

schema: The Oracle database account for Oracle9iAS Portal
password: The Oracle9iAS Portal account password
connect_string: The connect string to the database instance where the Oracle9iAS Portal repository is installed; specified as host_name:port:SID

Failure to Automatically Register the Files Portlet

After installing the Oracle Files middle tier, the Oracle Files domain is not started by default. Because of this the Web Client configuration assistant might not be able to contact the Files portlet during the Web Client configuration, causing the automatic registration of the Files portlet to fail.

If Oracle Files and the Web Client are Configured on Different Hosts

If Oracle Files and the Web Client are configured on different hosts, be sure to start the Oracle Files domain before you configure the Web Client.

See Also:

"Start All Necessary Processes" in the Configuring Oracle Files chapter of the Oracle Collaboration Suite Installation and Configuration Guide for more information.

If Oracle Files and the Web Client are Configured on the Same Host

If Oracle Files and the Web Client are configured on the same host during the same installation, automatic registration of the Files portlet fails.

Workaround:

Start the Oracle Files domain. Refer to the section called "Start All Necessary Processes" in the Oracle Files chapter of the Oracle Collaboration Suite Installation and Configuration Guide for more information.
Verify that the URL for Oracle Files are correctly set in the $ORACLE_HOME/webclient/classes/oracle/collabsuite/webclient/resources/webclient.properties file.
Re-run the Web Client configuration assistant from the command line:

$ORACLE_HOME/webclient/bin/webclient_installer.sh

Broken Images on UNIX

The Web Client uses Oracle UIX (User Interface XML) technology to generate web pages. UIX dynamically generates many images, such as buttons and tabs, appearing throughout the UI. Because of limitations in Java 2 Standard Edition (J2SE) before version 1.4, UIX requires an X server process to generate dynamic images on UNIX platforms.

To locate the X server, the UIX runtime relies on the value of the DISPLAY environment variable. If the Web Client is running on a UNIX host, and some of the images in the UI appear broken or inconsistent, the problem might be that the value of the DISPLAY environment variable for the Web Client process is set incorrectly.

A common symptom of this problem is that instead of the rounded, beige buttons, UI pages are rendered using native browser buttons.

To verify the value of the DISPLAY environment variable for the Web Client process, open the $ORACLE_HOME/opmn/conf/opmn.conf file in a text editor, and locate the entry for the instance called \OC4J_Portal\:

<oc4j maxRetry="3" instanceName="OC4J_Portal" gid="OC4J_Portal" numProcs="1">
  <environment>
    <prop name="DISPLAY" value="your-host-name:0.0"/>
  </environment>
</oc4j>

The value of the DISPLAY property should reference a running X server.

Note:

During installation, the Oracle Universal Installer automatically populates the value of the DISPLAY property in opmn.xml using the value of the DISPLAY environment variable detected during the installation session. If you are running the Oracle Universal Installer remotely, such as from a desktop PC with X emulation software (such as Hummingbird Exceed), this auto-detected value will be incorrect, because it will reference a remote X server that is not guaranteed to be available. The safest approach is to create an X server on the middle tier host and reference it in the DISPLAY property. Consult your UNIX documentation for information about how to start an X server on your platform.

Broken Link on Collaboration Suite Welcome Page

In the Oracle Collaboration Suite welcome page at http://host:port/, the link in the End-User Login portlet only functions on the host where Oracle Portal is configured. On other middle tier hosts, the link is broken.

Oracle9iAS Web Cache Start Failure

When starting Oracle9iAS Web Cache, you might see the following error:

Error: No matching CACHE element found in webcache.xml for current hostname and ORACLE_HOME. Cache Server failed to start

If you see this error, some parameters in webcache.xml might be pointing to symbolic links rather than actual paths.

To find out whether webcache.xml parameters point to symbolic links, perform the following steps:

Navigate to $ORACLE_HOME/webcache and open webcache.xml.
Check the path specified for the ORACLE_HOME environment variable.
At the command line, use the ls -l command to see if the top-level directory is a symbolic link. For example, if the value for ORACLE_HOME is /home/test/csr2mt, type the following command:
```
ls -l /home
```
If the directory is a symbolic link, you will see notation similar to the following:
```
test -> /private/test
```
If the webcache.xml parameters point to symbolic links, update all paths in this file to use the actual path instead of the symbolic link. For example, change all instances of /home/test/csr2mt to /private/test/csr2mt.

Note:
Back up the file before editing it. As paths are listed for multiple parameters in webcache.xml, make sure that you replace all occurrences.
Save webcache.xml.

Restart Oracle9iAS Web Cache:

$ORACLE_HOME/webcache/bin/webcachectl stop
$ORACLE_HOME/webcache/bin/webcachectl start

Restart OPMN:

$ORACLE_HOME/opmn/bin/opmnctl stopall
$ORACLE_HOME/opmn/bin/opmnctl startall

Oracle Enterprise Manager for Oracle Email Not Invoked

Oracle Enterprise Manager for Oracle Email is not invoked during the installation of Oracle Collaboration Suite Release 2 infrastructure.

Workaround:

Perform the following steps on the infrastructure and the middle tier:

Set the ORACLE_HOME environment variable.
Run the $ORACLE_HOME/oes/bin/install_umemd.sh script.
Restart Oracle Enterprise Manager:
```
$ emctl start
```

Referenced Name Error Occurs During Email Upgrade

During the mail store upgrade, the following error message occurs:

ORA-29521: referenced name could not be found

Workaround:

None, you can ignore errors in the $ORACLE_HOME/oes/log/upgrad904.log file.

Database is Not Being Registered

When running the database configuration assistant (DBCA) standalone, the database is not being registered.

Workaround:

Register the database using a user DN that is a member of the Oracle Directory Manager OracleDBCreators group, or the cn=orcladmin user DN.

Database Configuration Assistant Error

When the database configuration assistant (DBCA) is invoked from the Oracle Universal Installer or the command line, the following error occurs:

Open Wallet Failed

Workaround:

None, you can ignore this error message.

Single Sign-On Photograph Registration

The current release does not permit a photograph of a single sign-on user to be uploaded.

Create or Edit User Information in Delegated Administration Service

When clicking Create or Edit in the Resource Access Information section on the user creation and editing screens, the previously entered user data in the other fields on the screen is lost.

Workaround:

Re-enter the user data after the resource access information is created or edited.

File Not Found Error Occurs During Execution of the root.sh Script

When executing the root.sh script, you might receive an error message stating that the $ORACLE_HOME/rdbms/filemap file could not be found. This occurs because an attempt has been made to remove a file that does not exist.

Workaround:

None, you can ignore this error message.

Welcome Page iSupport Link

On the infrastructure and middle tier, where the Web Client is installed, perform the following:

Edit the $ORACLE_HOME/Apache/Apache/htdocs/index.html file by replacing the URL:

http://gsi.oraclecorp.com/OA_HTML/ibulogin.jsp

with the following:

http://www.oracle.com/support/metalink/index.html

Port Number Changes When Upgrade Assistant is Executed

When the upgrade assistant is executed, the port numbers for the following applications change:

Oracle CalendarOracle EmailOracle FilesOracle Web ConferencingOracle9iAS Wireless and Voice

Workaround:

Before running web client installer from the command line, manually reset the port number for each application in the $ORACLE_HOME/webclient/classes/oracle/ collabsuite/webclient/resources/webclient.properties file.

In the webclient.properties file, enter the appropriate port number in the URL associated with each of the following entry points:

mail.help.url
files.help.url
calendar.help.url
imeeting.help.url
search.help.url
wireless.help.url
mail
calendar
files
search
wireless
portal
imeeting
mail.provider
files.provider
search.provider
wireless.provider
webclient.provider
imeeting.provider
calendar.provider

Configure Oracle Collaboration Suite Components with SSL

See the following documentation for information about configuring Oracle Collaboration Suite components with SSL:

Security Web Providers document on the Oracle9iAS Portal Web site at the following URL: http://portalstudio.oracle.com
"Manually Setting Up HTTPS with mod_osso on the Middle Tier" in Chapter 6 of the Oracle Collaboration Suite Installation and Configuration Guide
"Installing Oracle Collaboration Suite" in the Oracle Collaboration Suite Installation and Configuration Guide
Section 5.6, "Configuring Ports and Network Connectivity" and Section 5.7, "Configuring SSL" in Chapter 6 "Sample Deployments" of the Oracle Web Conferencing Administrator's Guide

Linux Only: Upgrading Oracle Calendar

If you want to use the Upgrade Assistant to upgrade Oracle Calendar from Oracle Collaboration Suite 9.0.3, set the permissions of the /users directory and all its subdirectories to 755 before running the Upgrade Assistant.

Linux Only: Oracle Enterprise Manager Process Running Query Check Might Hang

When installing Oracle Collaboration Suite Release 2 Patch Set 1 in the infrastructure which was upgraded from Release 1 (9.0.3) to Release 2 (9.0.4 ), if the Oracle Enterprise Manager (EM) process is running, the EM process running query check might hang.

Workaround:

Shut down the Enterprise Manager process before installing Patch Set 1.

HP-UX Only: Pre-Requisite Failure in 11.0 System When Using $ORACLE_HOME/oui/bin/runinstaller

When using the runInstaller program from the $ORACLE_HOME/oui/bin directory, the installer exits with the following message:

Checking Operating System Version: must be B.11.11.    Actual B.11.00  Failed <<<<

To resolve this, modify the $ORACLE_HOME/oui/oraparam.ini file to include B.11.00 in the line containing B.11.11.

Documentation Errata

Page 11 in Appendix F of the Oracle Collaboration Suite Installation and Configuration Guide contains the following text:

"For HP platforms, after you complete step 4, unmount Disk 1, eject Disk 1, and mount Disk 5."

This is incorrect. The text should read as follows:

"For HP platforms, after you complete step 4, unmount Disk 1, eject Disk 1, and mount Disk 6."

Known Bugs in 9.0.4.1

The following are known suite-level bugs in Oracle Collaboration Suite 9.0.4.1.

Table 1-13 Known Suite-Level Bugs

Bug No.	Description
2499191	The Oracle Email `umbackend.tar` file in the Oracle Collaboration Suite 9.0.4.1 release is only in English. Workaround: Contact your Oracle support representative to obtain the patch. Refer to bug number 3156779.
2499206	The Oracle Email `umconfig.sh` script is only in English
3050374	In Internet Explorer, the single sign-on authentication returns an error for HTTPS links Workaround: Use two host names, one for the infrastructure and one for the middle tier. Obtain a second host name that is mapped to the same IP address in DNS. For the infrastructure, change all the host names entries to the second host name. Change all the host names in the OHS configuration. Re-register the `mod_osso` partner applications in the middle tier to pick up the changed single sign-on server name.
3116499	Intermittent installation problem results in an "Out of memory" error for the `dcmctl updateconfig` file Workaround: Increase the JVM memory.
3118140	The following error occurs when editing a user entry by changing only the password field. "Invalid Number Format for attribute : Employee Number" Workaround: To configure the employee number field to be alphabetical, perform the following steps: Log into DAS as a user with DAS configuration privileges such as `orcladmin`. Click the Configuration tab. Click the User Entry tab. Click the Next button on the lower right corner. In the attribute configuration table, select the attribute employee number row. Choose Single Line Text from the dropdown list in the UI Type column. Click Next in all subsequent windows, and click Finish.
3129911	Compilation error in the `WK_CRW` package body. Workaround: Log in to the database as `sys`. Enter the following SQL commands: SQL> grant select on SYS.DBMS_LOCK_ALLOCATED to WKSYS; SQL>alter package wksys.wk_crw compile body; SQL> alter package wksys.wk_snapshot compile body;
3151836	When installing Oracle Collaboration Suite on a system with a large memory, the Oracle Universal Installer displays an error message Workaround: Ignore the error message and continue installation
3204943	The `NLS_LANG` must be set to `AMERICAN_AMERICA.UTF8` to back up and restore multibyte messages and folders
3207537	An Oracle Internet Directory Delegated Administration Services error occurs on Simplified Chinese locale. Workaround: Uncomment the following line from the `httpd.conf` file in the `$ORACLE_HOME\Apache\Apache\conf` directory: include "ORACLE_HOME\Apache\Apache\conf\mod_osso.conf" Restart the HTTP Server through Oracle Enterprise Manager.
3214446	Linux only: When running the Files Configuration Assistant (`$ORACLE_HOME/ifs/files/bin/ifsca`) from Oracle Universal Installer or the command line, the following error message appears: exort: command not found Workaround: Ignore the error message.
3376394	When viewing the status of a transaction created and recorded in Oracle Enterprise Manager (for example, logging into and out of Calendar) the transaction status shows "down." The following error message appears: `NullPointerException` Performing the following workaround before creating a transaction prevents this error from occurring: For web applications that use ASCII-based character sets or UTF-8, add the flag `-DUrlTiming.CharacterConversion=0` to the `agentJavaDefines` variable in the agent `emd.properties` file.

Known Bugs in 9.0.4.2

Table 1-14 lists known suite-level bugs in Oracle Collaboration Suite Release 2 (9.0.4.2) Patch Set 1.

Table 1-14 Known Bugs in Release 2 (9.0.4.2) Patch Set 1

Bug No. Description

3376394

Bug No.	Description
3376394	As described in Oracle Enterprise Manager Managing Oracle Collaboration Suite, you can monitor your Oracle Collaboration Suite components using the Oracle Enterprise Manager Grid Control Console. However, if you create a Web Application target in the Grid Control Console and create business transactions to monitor the availability of your Oracle Calendar applications, you might run into the following problem. When viewing the status of a transaction (for example, a transaction that logs in and out of Oracle Calendar) the transaction status indicates that the Web Application is "down." When viewing the error, the following message appears: `NullPointerException` This problem often appears for Web Applications that use ASCII-based character sets or UTF-8. To fix this problem: Use a text editor to open the following file in the home directory of the Management Agent that is monitoring the Oracle Calendar Web Application: $ORACLE_HOME/sysman/config/emd.properties Locate the agentJavaDefines variable in the `emd.properties` file. For example: agentJavaDefines=-Doracle.dms.refresh.wait.time=1000 -DUrlTiming.UseJSSE=true Add the following parameter to the agentJavaDefines variable: -DUrlTiming.CharacterConversion=0 For example: agentJavaDefines=-Doracle.dms.refresh.wait.time=1000 -DUrlTiming.UseJSSE=true -DUrlTiming.CharacterConversion=0 Save and close the `emd.properties` file. Restart the Management Agent.

As described in Oracle Enterprise Manager Managing Oracle Collaboration Suite, you can monitor your Oracle Collaboration Suite components using the Oracle Enterprise Manager Grid Control Console. However, if you create a Web Application target in the Grid Control Console and create business transactions to monitor the availability of your Oracle Calendar applications, you might run into the following problem. When viewing the status of a transaction (for example, a transaction that logs in and out of Oracle Calendar) the transaction status indicates that the Web Application is "down." When viewing the error, the following message appears:

NullPointerException

This problem often appears for Web Applications that use ASCII-based character sets or UTF-8. To fix this problem:

Use a text editor to open the following file in the home directory of the Management Agent that is monitoring the Oracle Calendar Web Application:
```
$ORACLE_HOME/sysman/config/emd.properties
```

Locate the agentJavaDefines variable in the emd.properties file.

For example:

agentJavaDefines=-Doracle.dms.refresh.wait.time=1000 -DUrlTiming.UseJSSE=true

Add the following parameter to the agentJavaDefines variable:

-DUrlTiming.CharacterConversion=0

For example:

agentJavaDefines=-Doracle.dms.refresh.wait.time=1000 -DUrlTiming.UseJSSE=true -DUrlTiming.CharacterConversion=0

Save and close the emd.properties file.
Restart the Management Agent.