| Oracle® Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.1) for Windows Part Number B14386-02 |
|
|
View PDF |
| Oracle® Collaboration Suite Readme Release 2 Patch Set 1 (9.0.4.2.1) for Windows Part Number B14386-02 |
|
|
View PDF |
This section contains preinstallation requirements for the various components of Oracle Collaboration Suite.
|
Note:
Search OracleMetaLink at
Oracle recommends checking OracleMetaLink periodically for new patch sets and updates to Oracle Collaboration Suite. |
|
See Also: Oracle Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1) for complete preinstallation instructions |
This section includes the following topics:
Section 1.1, "Oracle Enterprise Manager Preinstallation Information"
Section 1.2, "Oracle Collaboration Suite Web Client Preinstallation Information"
Section 1.3, "Oracle Collaboration Suite Web Client Preinstallation Tasks"
Section 1.4, "Oracle Collaboration Suite Information Store Preinstallation Tasks"
Section 1.6, "Oracle Calendar Application System Preinstallation Requirements"
Section 1.9, "Oracle Web Conferencing Preinstallation Requirements"
Section 1.10, "Oracle9iAS Wireless Preinstallation Requirements"
Oracle Universal Installer detects whether Oracle Enterprise Manager is running when you attempt to install the patch set on the infrastructure and the middle tier, and warns you to shut it down before proceeding.
|
Note: For silent installations of the patch set, ensure that Oracle Enterprise Manager is shut down prior to installation. When installation is complete, restart Oracle Enterprise Manager. |
If you chose to configure the Oracle Collaboration Suite Web client when you installed Oracle Collaboration Suite, the patch set will upgrade the Web client.
A port number must be explicitly defined for the URL associated with each of applications listed in the Web Client page. After installing the patch set, HTTP and HTTPS ports (port 80 and port 443, respectively) are not appended by default to the URL. Therefore, if a port number is not explicitly defined for the URL associated with each application in the Web Client page, no port number automatically appends to the server hostname for the application.
To define port numbers for the URL:
Open the webclient.properties file located in:
%ORACLE_HOME%\webclient\classes\oracle\collabsuite \webclient\resources
Enter a port number for the URL for each of the portlet providers and application links.
If you have defined the port numbers correctly, the URL appear as in the following example for Web Conferencing:
http://imeetingserver.com:80
Before installing the patch set, you must verify that SYS privileges have been granted to the logminer based e-mail recovery packages. If privileges have not been granted, logminer based e-mail recovery will not function. The following procedure explains how to check for SYS privileges and grant the missing privileges. The procedure must be performed from the mailstore ORACLE_HOME environment.
To identify whether necessary privileges have been granted to the logminer recovery database objects, execute the following query from the SQLPLUS as SYS user.
SQL> SELECT object_name , owner FROM dba_objects WHERE object_name = 'LMMR_SETUP' AND object_type = 'PACKAGE';
If the actions in Step 1 return no rows then do the following:
cd %ORACLE_HOME%\oes\install\sql
From the SQLPLUS as SYS user:
SQL>@install_backend_sys.sql
If the preceding procedure is not done, the patchset installation will display an error in the upgrade9042.log file as shown in the following example.
507/5 PL/SQL: SQL Statement ignored 509/14 PL/SQL: ORA-00942: table or view does not exist creating package body MAIL_RECOVERY Warning: Package Body created with compilation errors. Errors for PACKAGE BODY MAIL_RECOVERY: LINE/COL ERROR 108/21 PLS-00201: identifier 'SYS.V_$LOGMNR_CONTENTS' must be declared 108/21 PL/SQL: Item ignored 109/21 PLS-00201: identifier 'SYS.V_$LOGMNR_CONTENTS' must be declared 109/21 PL/SQL: Item ignored
This section covers the following Oracle Calendar server preinstallation topics:
Section 1.5.1, "Installing the Patch Set while the Oracle Calendar Server Is Running"
Section 1.5.3, "Upgrading Oracle Calendar from Version 9.0.3 to 9.0.4.2.1"
Section 1.5.4, "Changes in Hardware Requirements for Upgrades"
|
Note: Prior to installing the patch set, it is mandatory to install Calendar patch 4002009 for 9.0.4.1.1. If you have not already done so, go to http://metalink.oracle.com , navigate to the Patches web page, and download the patch listed under Patch Number 4002009 onto the ORACLE_HOME on which you installed Oracle Calendar Release 2 (9.0.4.1.1) |
It is not necessary to stop the Oracle Calendar server before installing the patch set. The installation program automatically stops and restarts the Oracle Calendar server.
If you previously made changes to the %Oracle_Home%\ocal\misc\unison.ini file, the installation program recognizes this and modifies the file with any necessary parameter changes.
The following files are not overwritten when installing the patch set:
user.iniresource.inieventcal.iniThe following files are always overwritten when installing the patch set:
timezone.initimezone_os.iniUpgrade Oracle Calendar from version 9.0.3 to 9.0.4.2.1 as described in the following steps.
Install Oracle Calendar Release 2 (9.0.4.1.1) into a different ORACLE_HOME from your existing installation, as described in the Oracle Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1).
If you have not already done so, go to http://metalink.oracle.com, navigate to the Patches web page, and download the patch listed under Patch Number 4002009 onto the ORACLE_HOME on which you installed Oracle Calendar Release 2 (9.0.4.1.1).
Install Oracle Collaboration Suite Release 2 Patch Set 1 (9.0.4.2.1) over Release 2 (9.0.4.1.1).
Verify that the 9.0.3 and the 9.0.4.2.1 Calendar servers are down.
Run OcalPreUpg.cmd from the Calendar 9.0.4.2.1 %ORACLE_HOME%\ocal\upgrade directory.
Run ocsua.bat from the 9.0.4.2.1 %ORACLE_HOME%\upgrade directory.
If you do not follow these steps, unexpected behavior may result. For instance, if you upgrade your data to Release 2 (9.0.4.1.1) and then install the patch set, users will no longer be able to log in as event calendars or resources because the corresponding passwords will be lost. The passwords can, however, be reset using the Oracle Calendar Administrator.
If you upgrade before applying the patch set, you must copy the [CONFERENCING] section of the backed up 9.0.4.1 unison.ini to the 9.0.4.2.1 unison.ini.
Before you upgrade, Oracle recommends that you re-evaluate your sizing calculations based on the requirements provided for the new software. For CPU usage, the hardware requirements have changed as a result of added functionality, as follows:
If you are upgrading from Oracle Calendar 5.x or 9.0.3 to release 9.0.4.2.1, an increase in CPU usage is expected. If in your current Oracle Calendar 5.x or 9.0.3 installation you track regular peaks in CPU usage at 60% or greater, several times a day, additional CPU capacity might be required for this upgrade.
An upgrade to 9.0.4.2.1 from Calendar 5.x or 9.0.3 requires approximately four times the current disk space.
|
See Also: Oracle Calendar Administrator's Guide Release 2 (9.0.4) |
This section covers the following Oracle Calendar application system preinstallation topics:
|
Note: Prior to installing the patch set, it is mandatory to install Calendar patch 4002009 for 9.0.4.1.1. If you have not already done so, go to http://metalink.oracle.com , navigate to the Patches web page, and download the patch listed under Patch Number 4002009 onto the ORACLE_HOME on which you installed Oracle Calendar Release 2 (9.0.4.1.1) |
An issue resolved by this patch set is that of time zone behavior on the Oracle Calendar portlet (bug 3088332). For this particular fix to work, you must add the following xml text (if it is not already present) to the $ORACLE_HOME/config/jazn-data.xml%ORACLE_HOME%\config\jazn-data.xml file before the </jazn-policy> tag at the end of this file. This must be done on the Oracle9iAS Portal middle tier that runs the Oracle Calendar portlet before you install the patch set. Back up the file before making any changes. Replace the %ORACLE_HOME% with the physical Oracle home of the middle tier.
|
Note: This is only necessary if you are running the Oracle Calendar portlet. |
<grant>
<grantee>
<codesource>
<url>file:%ORACLE_HOME%\webclient\lib\webclient_common.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.ias.repository.schemaimpl.CheckRepositoryPermission</class>
<name>connectAs</name>
</permission>
</permissions>
</grant>
If you are running Oracle9iAS Portal on a different middle tier, you must copy two newly installed files over to that middle tier after installation, as described in Chapter 3, "Patch Set Postinstallation Instructions".
Oracle Internet Directory on the infrastructure server must be running prior to installing the patch set.
|
Note: For silent installations of the patch set on the middle tier, ensure that Oracle Email servers are stopped prior to starting the patch set installation on the middle tier. |
|
See Also: Oracle Email Administrator's Guide for instructions on how to stop Oracle Email processes |
It is necessary to stop the e-mail servers before installing the patchset on the information store that the middle tier is serving. If the information store is being served by multiple middle tiers running e-mail servers, all e-mail servers on these middle tiers need to be shutdown prior to installing the patch set on the information store.
It is normally not necessary to stop the Oracle Email servers on the middle tier before installing the patch set on that middle tier. Normally, the installation program automatically stops all Oracle Email servers at the beginning of the installation and restarts them when installation is complete. This will not be the case if the existing configuration uses non-qualified hostnames, for example, a hostname missing the domain suffix as part of an e-mail service target name. To check whether non-qualified hostnames exist, run the following command from a command prompt window:
oesctl show targets
If the output contains non-qualified hostnames, shutdown the server prior to performing the upgrade.
On Windows NT 4.0 only, you must shut down e-mail server processes before installing the patchset on the middle tier. Restart e-mail server processes after installing the patchset on the middle tier. This procedure does not apply to Windows 2000 or Windows 2003 Enterprise Edition or Standard Edition.
Ensure that the following requirements are met prior to installing the patch set:
The database server must be running.
If you have customized the Oracle Files Web interface, you must back up the customized files before applying the patch set, then restore the files to their original locations after the patch set has been installed.
|
See Also: Oracle Files Administrator's Guide for information about customizing the Oracle Files Web interface |
All Oracle Files processes, including the Oracle Files domain, regular nodes, and HTTP nodes, must be stopped prior to installing the patch set. To see whether Oracle Files processes are running, execute the following commands:
ifsctl status -n from %ORACLE_HOME%\ifs\files\bin to see whether the Oracle Files domain and regular nodes are running
dcmctl getState -co OC4J_iFS_files -v from %ORACLE_HOME%\dcm\bin to see whether the Oracle Files HTTP node is running
To stop the Oracle Files domain and regular nodes, follow these steps:
If it is not running already, start Oracle Enterprise Manager by executing the following command:
%ORACLE_HOME%\bin\emctl start
Using a Web browser, access the Oracle Enterprise Manager Web site at http://host_name:port, where host_name is the name of the Oracle Files middle-tier computer. The port is typically 1810.
Enter the authentication information in the pop-up window. The user name is typically ias_admin.
Click the name of the application server instance where Oracle Files is running. The Oracle9iAS Home Page appears.
Click the Oracle Files domain link. The domain appears in the following format:
iFS_db_host_name:port:db_service_name:files_schema
Click Stop Domain.
Click OK.
Stop Oracle Enterprise Manager before installing the patch set. Use the following command to stop Oracle Enterprise Manager:
%ORACLE_HOME%\bin\emctl stop
To stop Oracle Files HTTP nodes, follow these steps on each Oracle Files middle tier:
From the Oracle9iAS Home Page on the Oracle Enterprise Manager Web site, select OC4J_iFS_files.
Click Stop. On the Warning page, click Yes to stop the OC4J instance.
Alternatively, you can use the following commands from the command line:
%ORACLE_HOME%\ifs\files\bin\ifsctl stop %ORACLE_HOME%\dcm\bin\dcmctl stop -co OC4J_iFS_files -v -t 360
This section includes the following topics:
Section 1.9.1, "Shut Down Oracle Real-Time Collaboration Services"
Section 1.9.2, "Required Disk Space on Information Storage Database Server"
Section 1.9.3, "How Installation Interacts with Oracle Internet Directory"
Ensure that the following requirements are met prior to installing the patch set:
You have at least 1 GB of space on your information storage database host
|
See Also: Section 1.9.2, "Required Disk Space on Information Storage Database Server" for more details on disk space requirements |
You have access to the password for the Oracle Internet Directory administrator account, and the Oracle Directory Integration and Provisioning server must be running on the Oracle Internet Directory system
|
See Also: Section 1.9.3, "How Installation Interacts with Oracle Internet Directory" for more details |
You have installed the patch set to all Real-Time Collaboration middle tiers. You cannot use middle tiers with multiple versions of the Oracle Web Conferencing system if those middle tiers use the same database, because the schema has been updated for this patch set. Specifically, a middle tier running Oracle Collaboration Suite Release 2 (9.0.4.1.1) cannot share an information storage database with a middle tier running the patch set.
In addition, you must perform the following tasks before installing the patch set:
Back up your information storage database. At a minimum, remember to back up the Oracle Real-Time Collaboration RTC and RTC_APP schemas. You may need this backup if you have to restore the system in case of fatal patch failure.
Retrieve all certificates that were imported into the %ORACLE_HOME% \imeeting\conf\certdb.txt file so that you can reimport them after the patch set is applied.
|
See Also: Oracle9iAS Web Cache Administration and Deployment Guide (9.0.2) for more details |
Make a backup copy of the %ORACLE_HOME%\imeeting\conf \certdb.txt file.
Shut down all Oracle Real-Time Collaboration services and instances on each ORACLE_HOME to which you are applying the patch set.
Before installing the patch set, you must shut down all Oracle Real-Time Collaboration services and instances in your Oracle Collaboration Suite setup (that is, on each ORACLE_HOME with Oracle Real-Time Collaboration installed).
Stop all Oracle Real-Time Collaboration servers, both core components and document and voice conversion servers (if used), as follows:
%ORACLE_HOME%\imeeting\bin\imtctl stop|
Note: If you cannot shut down the processes and you know that there are no Oracle Real-Time Collaboration instances running, you may have to manually terminate the processes using your operating system tools. |
Stop the Oracle Real-Time Collaboration OC4J instance, as follows:
%ORACLE_HOM%\dcm\bin\dcmctl stop -co OC4J_imeeting -t 360 -v|
See Also: Oracle9iAS Web Cache Administration and Deployment Guide for more details |
During installation, the following tablespaces with the following initial sizes are created for Oracle Web Conferencing in the information storage database. You must have at least 1 GB of free space in the directory that you specify as the tablespace location while running the Oracle Universal Installer.
Table 1-1 Default Tablespace Sizes for Oracle Web Conferencing
| Tablespace Name | Default Size (MB) |
|---|---|
rtc_lookup_data |
16 |
rtc_lookup_index |
8 |
rtc_transaction_data |
256 |
rtc_transaction_index |
64 |
rtc_archive_data |
64 |
rtc_archive_index |
16 |
rtc_document_data |
64 |
rtc_document_index |
8 |
rtc_recording_data |
64 |
rtc_recording_index |
8 |
rtc_transient_data |
128 |
rtc_transient_index |
32 |
rtc_transient_lob_data |
64 |
rtc_transient_lob_index |
8 |
rtc_report_data |
64 |
rtc_report_index |
8 |
rtc_temp |
128 |
| TOTAL SIZE REQUIRED | 1000 MB (1 GB) |
The preceding tablespaces are created with the AUTOEXTEND setting ON and a maximum file size of 2 GB. Make sure you have enough space available for future expansion. Depending upon your use of the system, you may want to increase the size of the tablespaces.
As the Oracle Real-Time Collaboration installation process runs, it uses the Oracle Internet Directory administrator account to do the following tasks in the Oracle Internet Directory installation. The files listed below are located in the following directory, %ORACLE_HOME%\imeeting\install\oid, on the Oracle Real-Time Collaboration core components installation.
rtccontainer.ldi (creates a container named RTC)
rtcentity.ldi (creates an entity named RTCApplication in the RTC container)
install_rtc_oid.cmd (sets up an Oracle Directory Integration and Provisioning process between the Oracle Internet Directory and Oracle Real-Time Collaboration services)
As noted previously, you must make sure the Oracle Directory Integration and Provisioning server is running on the Oracle Internet Directory system before running the installation, otherwise the installation process may suspend.
The Oracle Web Conferencing system stores the following data about Web conferencing users in its information store, to improve performance:
The Oracle Real-Time Collaboration services use the Oracle Directory Integration and Provisioning service offered by Oracle Internet Directory to synchronize the data in the information store in case any of the data changes (for example, an e-mail address change).
Access information is not automatically retrieved when the patch set is applied. Prior to applying the patch set, ensure that your information is correct and make a copy of the portal.properties file, found in the %ORACLE_HOME%\wireless\server\classes\messages directory.
Using Enterprise Manager, shut down OC4J_Wireless, all Messaging Server instances, and the PIM Notification Dispatcher process.
