4 Applying the 9.0.4.2 Patch Set

This chapter supplements the instructions in the readme file for applying the 9.0.4.2 patch set. It contains the following sections:

Section 4.1, "Downloading and Applying the 9.0.4.2 Patch Set"
Section 4.2, "Configuring Oracle Web Conferencing Real-Time Collaboration After Applying the Patch Set"

4.1 Downloading and Applying the 9.0.4.2 Patch Set

You can download the 9.0.4.2 patch set from

http://metalink.oracle.com/

On the Patches Web page of this Web site, search for patch set number 3564610 for your platform.

The 9.0.4.2 patch set must be applied on each host in the Oracle Collaboration Suite environment. To apply this patch set:

Read the instructions in the readme file.
Back up all the tiers.
Ensure that the prerequisites mentioned in the readme file are met.

These prerequisites include a recommendation to upgrade the Information Storage database to 9.2.0.5 by using the 3501955 patch.

Follow the instructions on creating the Oracle Web Conferencing Real-Time Collaboration volumes and tablespaces given in Appendix D. These raw volumes and tablespaces are required by the Information Storage database for Oracle Web Conferencing Real-Time Collaboration.

Note:

If you have a clustered file system on which volumes need not be created manually, then you can skip this step. For example, Oracle Cluster File System on Linux is a clustered file system that does not require manual creation of volumes.

Apply the patch set to the Infrastructure node. Do not shut down the database before you perform this step.
Apply the patch set to the Information Storage database tier.
Install the 9.0.4.2 patch set on the Oracle Calendar Server and Oracle Files Domain Controller tier.
Install the patch set on all the Middle Tiers.
Follow the post-installation instructions given in the readme file.

4.2 Configuring Oracle Web Conferencing Real-Time Collaboration After Applying the Patch Set

To use an Oracle Real Application Clusters-enabled Information Storage, you must configure the Oracle Web Conferencing Real-Time Collaboration component after applying the patch set. To do this:

Shut down all Oracle Web Conferencing Real-Time Collaboration components on the current instance by running the following commands:
```
$ORACLE_HOME/imeeting/bin/imtctl stop
$ORACLE_HOME/dcm/bin/dcmctl stop -co OC4J_imeeting -v
```

Edit the $ORACLE_HOME/imeeting/conf/imtinit.conf file.

In this file, specify the full JDBC connection string. The following are sample contents of the imtinit.conf file:

oracle.imt.database.sid=str1
oracle.imt.instancename=OUIHome.ocslb.oracle.com
oracle.imt.schema.password.encrypted=27250A0179786675780C0272534812
oracle.imt.database.hostname=store1.oracle.com
oracle.imt.database.port=1521
oracle.imt.schema.name=rtc_app
oracle.rtc.instance.version=2.0.4.3.0

Note:

In the default configuration, connection information for the Oracle Web Conferencing Real-Time Collaboration database is specified in terms of the hostname, port, and sid properties. Oracle Web Conferencing Real-Time Collaboration 2.0.4.3 adds support for a new property called oracle.imt.database.jdbc.connect. When this property is present, the hostname, port, and sid properties are ignored even if they are present.

Add the following property in the imtinit.conf file:

oracle.imt.database.jdbc.connect=FULL_JDBC_CONNECT_STRING

Without any modification or validation, the value of FULL_JDBC_CONNECT_STRING will be used to establish connections to the Oracle Web Conferencing Real-Time Collaboration repository. This means that the value can be any valid JDBC 9.0.1.4 connection string. Unlike the entries in the tnsnames.ora file, the entire connection string must be specified on a single line in the imtinit.conf file.

The following is an example of the syntax you can use for specifying JDBC connection information. Substitute appropriate HOST, PORT, and SERVICE_NAME values in this syntax.

oracle.imt.database.jdbc.connect=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=store1.oracle.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=str.oracle.com)))

The following is sample JDBC connection information. Multiple listeners, each specified by its IP address, have been used in this example.

oracle.imt.database.jdbc.connect=jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=store1.oracle.com)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=store2.oracle.com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=str.oracle.com)))

The old database connection settings are usually ignored, but some commands may still expect these settings to exist for validation purposes. Therefore, do not change these connection settings.

Restart all Oracle Web Conferencing Real-Time Collaboration components on the current instance by running the following commands:
```
$ORACLE_HOME/imeeting/bin/imtctl start
$ORACLE_HOME/dcm/bin/dcmctl start -co OC4J_imeeting
```
Verify that the Oracle Web Conferencing Real-Time Collaboration components connected to the database are using the new connection string.

To do this on UNIX or Linux, first run the following command:
```
grep "Database Connection Info" \ $ORACLE_HOME/imeeting/logs/imtcontrol/*.xml
```
View the contents of the files returned by the command. The following are examples of entries that the older files must contain:
```
<record timestamp="2003-10-22T02:02:16.811-07:00" time-local="true"
severity="config" source-path="oracle.imt.application.db"
source="SrvDBConnProvider"><message>Database Connection Info:
jdbc:oracle:thin:@store1.oracle.com:1521:str1 (Schema rtc_app)</message>
```
The latest log file, which was created when you ran the imtctl start command, must contain an entry with the new JDBC syntax.

For example:
```
<record timestamp="2003-10-23T02:21:27.994-07:00" time-local="true"
severity="config" source-path="oracle.imt.application.db"
source="SrvDBConnProvider"><message>Database Connection Info:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_
LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=store1.oracle.com)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME=str.oracle.com))) (Schema rtc_app)</message>
```
Perform the same check on the OC4J_imeeting logs.

To do this on UNIX or Linux, run the following commands:
```
grep "Database Connection Info" \ $ORACLE_HOME/imeeting/logs/application/*.xml
```
If the new log files still contain the old connection string syntax, then recheck the previous steps to make sure that you specified the correct property, edited the correct file, and restarted all the Oracle Web Conferencing Real-Time Collaboration components. In addition, check your Oracle Web Conferencing Real-Time Collaboration version to ensure that you are using 2.0.4.3 or later. To do this, run the following command:
```
$ORACLE_HOME/imeeting/bin/imtctl versions
```
If the log files show that Oracle Web Conferencing Real-Time Collaboration is using the new connection string, then you have successfully completed all the steps.