Skip Headers
Oracle® Collaboration Suite Release Notes
10g Release 1 (10.1.1) for HP-UX
Part Number B19092-03
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
View PDF

2 Oracle Collaboration Suite Installation and Upgrade Release Notes

This chapter describes suite-level release note information affecting the installation and upgrade of Oracle Collaboration Suite. This chapter contains the following sections.

Note:

This document was updated on October 7, 2005.

2.1 Oracle Collaboration Suite Installation

The following topics describe release note information associated with Oracle Collaboration Suite installation.

2.1.1 New in Oracle Collaboration Suite Installation

The new features of Oracle Collaboration Suite installation include:

  • No Manual Configuration

    In Oracle Collaboration Suite, the main installation takes care of all tasks that were previously identified as post-installation tasks for each Applications tier component.

  • Option of Changing Ports During Installation

    You can specify custom port numbers for components, instead of having the installer assign default port numbers. This feature is called the static ports feature.

  • Improved Single Computer Installation

    For this release, single-computer installation is available for all platforms. Unlike earlier releases, it enables you to enter all required information at the beginning of the installation.

  • Changes in Applications Tier Installation

    The following functionality has been added to the Applications tier of Oracle Collaboration Suite:

    • Support for Oracle Mail configuration

    • Support for Oracle Content Services configuration

    • Support for selection of Oracle Collaboration Suite Databases to be used for components that you select

    • Support for selection of well-known ports during the installation

  • Support for High Availability Configurations

    In this release, Oracle Collaboration Suite supports the following high availability environments:

    • Oracle Calendar Cold Failover Cluster

    • Distributed Identity Management Architecture

    • Colocated Identity Management Architecture

    • Single Cluster Architecture

  • Support for Secure Installation

    You can specify that components connect to Oracle Internet Directory using Secure Socket Layer (SSL) only.

  • Enhancements in Configuration Assistants

    Manual configuration is not required for Oracle Collaboration Suite 10g Release 1 (10.1.1.0.2). The configuration assistants perform nearly all the post-installation tasks.

  • More Prerequisite Checks

    The installer performs more prerequisite checks to ensure that your computer meets the minimum requirements.

  • Support for Generating Installation Statistics

    The installer now provides command-line options for monitoring resources used for installation.

  • Support for Oracle Internet Directory Replication

    In this release, you can install the master Oracle Internet Directory, as well as Oracle Internet Directory replicas, using the installer.

2.1.2 Known Limitations and Workarounds in Oracle Collaboration Suite Installation

The following sections describe known limitations and workarounds for Oracle Collaboration Suite installation and configuration:

2.1.2.1 Oracle Support Installation Articles

Oracle Support has created the following articles on its MetaLink Web site at http://metalink.oracle.com. These articles describe, or will describe, important information and issues you may encounter during Oracle Collaboration Suite installation. These articles will be updated regularly by Support personnel and will be based on actual user experiences. Consult them regularly for important updates.

  • Note 331638.1 List Of Patches To Install On Top Of CollaborationSuite 10.1.1: Lists recommended Oracle Collaboration Suite patches.

  • Note 331666.1 How To Install Collaboration Suite 10gR1 (10.1.1): Provides additional hints for installation.

  • Note 330926.1 Known Issues for the Collaboration Suite MRCA (Metadata Repository Creation Assistant): For customers who want to install the Metadata Repository into an existing Oracle 10g database instead of the Infrastructure that is shipped with Oracle Collaboration Suite 10.1.1.

See Also:

Section 2.2.1.1, "Oracle Support Upgrade Articles"

2.1.2.2 Database Versions

Oracle Collaboration Suite 10g (10.1.1.0.2) requires an Oracle Database version of at least 10.1.0.4.2. This database version is automatically installed when customers install the database from the Oracle Collaboration Suite 10g media. Version 10.1.0.4.2 of Oracle Database can only be used with Oracle Collaboration Suite 10g.

Customers wishing to use their own existing database must upgrade that database to at least version 10.1.0.4.2 before using the "Enable Customer Database" option from the Installer. A patch set for this is on the Oracle Collaboration Suite 10g media.

Customers wishing to use a database on a platform not natively supported by Oracle Collaboration Suite will be able to use OcsDBSchemaReg in remote mode, once the remote database is upgraded to at least 10.1.0.5.

All customers will be required to upgrade databases used by Oracle Collaboration Suite 10g to 10.1.0.5 or 10.2 as those versions are made available for different platforms.

2.1.2.3 Enabling Databases

When choosing the "Oracle Collaboration Suite Enable Database" option during installation, make sure that Oracle Enterprise Manager has been installed into the database ORACLE_HOME. This is a requirement for successful installation.

Note:

Enabling databases is not supported against Real Application Clusters with RAW storage type.

2.1.2.4 Oracle Portal Requires Oracle Knowledge Base Component

If you choose to install your own RDBMS 10.1.0.2.0 (+ 10.1.0.4.2 patch) for use as a MetaData Repository for a distributed Identity Management installation, the Oracle Knowledge Base component needs to be installed into that database prior to running the MetaData Repository Configuration Assistant. The Oracle Knowledge Base component is located on the RDBMS Companion CD.

The Oracle Knowledge Base component is required for proper operation of the Oracle Portal that is part of Oracle Collaboration Suite.

See Also:

Section 2.1.2.11, "Application Server Metadata Repository Creation Assistant"

2.1.2.5 Correcting Oracle Messenger Sign-In Failure in a High Availability Environment

If you are unable to sign in to Oracle Messenger in a Single Cluster high availability, collocated Instant Messaging high availability, or distributed Instant Messaging high availability environment, perform the following workaround:

  1. Launch Oracle Real-Time Collaboration Control; for example:

    $ORACLE_HOME/imeeting/bin/rtcctl

  2. From Oracle Real-Time Collaboration Control, run getstate -v to fetch the ID number of the Oracle Presence Server (Instant Messaging router, imrtr).

  3. From Oracle Real-Time Collaboration Control, run stop -cid ID_number_for_imrtr.

  4. From Oracle Real-Time Collaboration Control, run start -cid ID_number_for_imrtr.

2.1.2.6 Oracle Enterprise Manager Grid Control Versions

To manage Oracle Collaboration Suite 10g Release 1 (10.1.1), you need to update Oracle Enterprise Manager Grid Control to version 10.1.0.4. You can install Oracle Enterprise Manager Grid Control version 10.1.0.3, which ships with Oracle Collaboration Suite. Then download and apply the Oracle Enterprise Manager Grid Control 10.1.0.4 patch set. You will need to patch both the Oracle Management Service and Management Agents.

To download the Oracle Enterprise Manager Grid Control 10.1.0.4 patch set, navigate to:

http://metalink.oracle.com/

2.1.2.7 Setting NLS and Operating System Locale Environment Variables Before Starting Management Processes

If in a non-English environment, you launch a command line tool such as emctl to start a process, make sure the operating system locale and NLS_LANG environment variable settings are configured properly and consistently. This is applicable to the emctl command line utility that is available with Oracle Application Server installations as well as with the emctl utility available with Grid Control Console installations.

If these environment variables are not set prior to Oracle Application Server or Grid Control Console installations, then non-ASCII characters will appear incorrectly in the Application Server Control Console or Grid Control Console, respectively. To prevent this problem from occurring, set these two environment variables prior to installation. If this is not possible, then to resolve the problem set the two environment variables after installation and restart the Management Agent.

Refer to the following sections for details on how to check and set the values for these variables:

2.1.2.7.1 Checking the Operating System Locale

Make sure the LC_ALL or LANG environment variables are set with the appropriate value. To check the current setting, issue the following command:

$PROMPT> locale
2.1.2.7.2 Setting the Operating System Locale

If you are using bash or zsh, to set the operating system locale environment variable, issue the export command. For example:

export LANG=zh_CN

In this example, the variable is being set to Simplified Chinese. For the specific value in each operating system, refer to operating system-specific documentation.

If you are using csh or tcsh, then issue the setenv command:

setenv LANG zh_CN
2.1.2.7.3 Checking the NLS_LANG Environment Variable

Make sure the NLS_LANG environment variable is set with the appropriate and compatible value with the operating system locale setting (and the Grid Control Management Repository database character set if Grid Control is being used to centrally manage the Oracle Application Server). For the specific value for the language or the character set, refer to the Globalization Support Guide of the Oracle product you are using.

If the platform is a Microsoft Windows-based operating system, the default NLS_LANG setting in the registry should be used as it is. You usually do not have to change the value.

In addition, check to see if the NLS_LANG setting exists in $ORACLE_HOME/opmn/conf/opmn.xml on UNIX or ORACLE_HOME\opmn\conf\opmn.xml on Windows. For example, the following content should appear in the opmn.xml file:

<environment>
     <variable id="TMP" value="/tmp"/> 
     <variable id="NLS_LANG" value="JAPANESE_JAPAN.JA16SJIS"/> 
</environment>

If the NLS_LANG setting exists, make sure the NLS_LANG setting in the opmn.xml file is identical to the NLS_LANG environment variable.

2.1.2.7.4 Setting the NLS_LANG Environment Variable

If you are using bash or zsh, to set the NLS_LANG environment variable, issue the export command. For example:

export NLS_LANG="Simplified Chinese_China.ZHS16GBK"

In this example, the variable is being set to Simplified Chinese. For the specific value in each operating system, refer to operating system-specific documentation.

If you are using csh or tcsh, then issue the setenv command. For example:

setenv NLS_LANG "Simplified Chinese_China.ZHS16GBK"

2.1.2.8 Custom Database Strings That Exceed 256 Characters

You cannot enable a custom database if the custom database connect string (as registered in OID in orclNetDescString) is longer than 256 characters, and the environment variable TNS_ADMIN is not set prior to the installation. (4538565)

2.1.2.9 Oracle Directory Integration and Provisioning Server Not Sending Provisioning Events due to Purged Change Log Entries

If you use time-based change log purging with version 3.0 provisioning profiles, change logs entries are purged before the Oracle directory integration and provisioning server propagates the changes to any provisioning-integrated applications. This occurs because Oracle Directory Integration and Provisioning does not create version 3.0 provisioning profile entries in the default cn=subscriber profile,cn=changelog subscriber,cn=oracle internet directory change log subscriber container. (4524793)

To resolve this problem, create a container in the default change log subscriber container for each version 3.0 provisioning profile and assign a value of 0 to each profile's orclLastAppliedChangeNumber attribute. The following sample LDIF file creates a provisioning profile container in the default change log subscriber container and assigns a value of 0 to the orclLastAppliedChangeNumber attribute:

dn: cn=profile_name,cn=changelog subscriber,cn=oracle internet directory
orclsubscriberdisable: 0
orcllastappliedchangenumber: 0
objectclass: orclChangeSubscriber

2.1.2.10 Installing or Upgrading using non-Oracle Internet Directory Superuser Accounts

The Oracle Internet Directory Schema Admins group (cn=OID Schema Admins, cn=groups, cn=OracleContext) is used to administer the LDAP schema in Oracle Internet Directory. The Oracle Internet Directory Super-User account is a member of this group, but you may add additional members to this group. (4539283)

Oracle Collaboration Suite components maintain their component LDAP schema version under cn=OracleSchemaVersion. As part of creating new Oracle Internet Directory schema elements, the components also update their component version. The Access Control policy on this container should allow members of the Oracle Internet Directory Schema Admins group to edit the schema version in addition to making changes to the LDAP schema. The out of box Access Control policy allows the members of this group to change the LDAP schema, but it does not allow updating the subtree under cn=OracleSchemaVersion.

As a result, if you install Oracle Collaboration Suite or any component using an account other than the Oracle Internet Directory superuser (orcladmin), one or more component Configuration Assistants may fail when they attempt to update the version number stored in Oracle Internet Directory.

Please run the following LDIF script using the ldapmodify tool before installing or upgrading Oracle Collaboration Suite components using an account other than orcladmin. Create an LDIF file with the following content:

dn: cn=OracleSchemaVersion
changetype: modify
replace: orclaci
orclaci: access to entry by group="cn=OID Schema Admins, cn=groups, cn=OracleContext" (browse, add)
orclaci: access to attr=(*) by group="cn=OID Schema Admins, cn=groups, cn=OracleContext" (search, read, write, compare)

Use ldapmodify to run this LDIF script by entering the following command:

ldapmodify -p <OID port> -h <OID host> -D cn=orcladmin -w <password> -f <name of the file containing above ldif record>

2.1.2.11 Application Server Metadata Repository Creation Assistant

The Application Server Metadata Repository Creation Assistant is not currently part of the Oracle Collaboration Suite media kit. Customers needing this should read Note 330926.1 on Oracle MetaLink at:

http://metalink.oracle.com

2.1.3 Known Issues in Oracle Collaboration Suite Installation

The following table lists suite-level known issues in Oracle Collaboration Suite installation and configuration.

Table 2-1 Known Issues in Oracle Collaboration Suite Installation

Description Action Bug Number

If an incorrect value is used for the TMPDIR environment value, installation errors will occur.

Make sure that TMPDIR is a valid, writable directory.

4637528

Oracle Universal Installer will not allow you to continue, and the following error message is generated:

Error connecting to the database that you have selected for Oracle Calendar Contacts and Provisioning. Please make sure that the database is up and running and the CALENDAR user account is unlocked or select another database.

Attempt this workaround only if the Oracle Calendar server Database Configuration Assistant was successful during the configuration of your Oracle Collaboration Suite Database.

Follow these steps on the effected Oracle Collaboration Suite Database before continuing with the installation:

  1. Set your ORACLE_HOME and ORACLE_SID.

  2. Ensure that you can connect to the desired instance with sqlplus. Exit sqlplus.

  3. From the $ORACLE_HOME/jdk/bin directory, run the following command:

    ./java  -classpath $ORACLE_HOME/jlib/ldapjclnt10.jar:$ORACLE_HOME/jlib/ojmisc.jar:$ORACLE_HOME/ocal/jlib/ocal_infostore.jar oracle.calendar.infostore.configuration.InfoStoreConf -t seed -oraclehome $ORACLE_HOME  -schemap <Schema password for Calendar chosen at install> -sysp <sysop password>

  4. Ignore the following warning if it is returned:

    javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused]
Warning: Relying on environment.

  5. Continue with your Applications tier installation.

4540312

During a standalone Oracle Calendar installation, you can choose which components of the Oracle Calendar application system you want to install. If you do not install all of them, and subsequently choose to install them into the same ORACLE_HOME in a second install session, then the configuration files are not instantiated. Also, the ocas.conf file is not updated to enable the associated component.

Workaround 1:

Always install all components of the Oracle Calendar application system at initial install. Even if you do not plan to use a component, the impact on disk space is minimal, and unused components can easily be disabled to reduce memory use.

The components are listed as plug-ins at the end of the $ORACLE_HOME/ocas/conf/ocas.conf file as follows. Comment out a plug-in to disable it.

[plugins]
plugin01 = ./liblexcaldata.so # Oracle Calendar app services
plugin02 = ./liblexwebhtml.so # Oracle Calendar Web Client
plugin03 = ./liblexxml.so     # Oracle Calendar Web Services
plugin04 = ./liblexsyncml.so  # Oracle Sync Server

Workaround 2:

If you must add Oracle Mobile Data Sync or Oracle Calendar Web services as installed components, do the following after installation:

  1. Change to the directory $ORACLE_HOME/ocas/conf.

  2. For Oracle Calendar Web services, make a copy of ocws.conf.sbs and name it ocws.conf, then add the following line to the [plugins] section of ocas.conf:

    plugin03 = ./liblexxml.so

  3. For Oracle Mobile Data Sync, make a copy of ocst.conf.sbs and name it ocst.conf, then add the following line to the [plugins] section of ocas.conf:

    plugin04 = ./liblexsyncml.so

4486120

You cannot install Oracle Calendar application system standalone into an ORACLE_HOME where the Oracle Calendar server has already been installed.

Install Oracle Calendar application system standalone into a different ORACLE_HOME.

4255307

On very slow computers, the Oracle Collaborative Portlets Configuration Assistant may fail on the first try.

The Configuration Assistant will often run successfully when re-tried.

4511516

The Oracle Collaboration Suite Console Configuration Assistant sometimes fails.

Select the component in question and retry the configuration assistant. If you then see the following error message, you should ignore the message and continue with the installation:

Output generated from configuration assistant "Collaboration Suite Console Configuration Assistant" (attempt 2):
Register OCS Integration class and create Apps Identity...0 [main] ERROR oracle.sysman.ocs.sdk.csc.install.OCSConfigAssistant  - Failed to create Component Entry
...
Base Exception : javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - Object already exists]
...
Configuration assistant "Collaboration Suite Console Configuration Assistant" failed

4502739

Oracle Universal Installer may report that the Oracle Discussions Configuration Assistant has successfully completed, when in fact the Discussions Web interface is not accessible, returning a "Page not found error".

Check the install log for the deployment of the Discussions J2EE application. If the deployment completed but with some errors, rerun the Oracle Discussions Applications tier Configuration Assistant by copying and pasting its invocation command as reported in the install log.

4511808

Oracle Universal Installer may report that the Oracle Workspaces Configuration Assistant has successfully completed, when in fact the Oracle Workspaces Web interface is not accessible, returning a "Page not found error".

Check the install log for the deployment of the Oracle Workspaces J2EE application. If the deployment completed but with some errors, rerun the Oracle Workspaces Applications tier Configuration Assistant by copying and pasting its invocation command as reported in the install log.

4443890

Selection of non-default Oracle Collaboration Suite Databases is not registered when clicking Next on the Select Component to Configure screen.

If multiple instances of Oracle Collaboration Suite Databases are available in Oracle Internet Directory, then when you click on the Database Name column and then select the correct database for each component from the drop-down list, the selection might not be retained. To ensure that the selection is retained, you must click the Database Name column again after selecting the required database for each component.

4283272

If you are installing an Applications tier and Oracle Internet Directory is in SSL-only mode, then apply patch 4493920 to the Oracle Collaboration Suite Database.

From Oracle MetaLink, download patch 4493920 and apply it to the upgraded Oracle Collaboration Suite Database according to the instructions contained in the patch ZIP file.

You should also apply this patch if you encounter any of the issues listed in Section 2.2.1.2 during or after the Applications tier installation. If the error occurs during the installation, exit the Oracle Universal installer, apply the patch and then restart the Oracle Universal installer.

4493920

If Oracle Internet Directory and the Oracle Collaboration Suite database use different SSL modes — for instance if you switch Oracle Internet Directory to SSL-only mode, but the Oracle Collaboration Suite database is configured as non-SSL — the Oracle Ultrasearch Configuration Assistant will not run successfully during Applications tier installation.

Update the Oracle Internet Directory mode information in the database as follows:

  1. Log in to the Oracle Collaboration Suite database as a dba user.

  2. Update the following values in the wk$sys_config table to the new OID settings: OID_PORT, OID_SSL_PORT, SSL_ONLY_MODE.

    OID_PORT: Oracle Internet Directory non-SSL port

    OID_SSL_PORT: Oracle Internet Directory SSL port

    SSL_ONLY_MODE: Y for SSL-only mode, N for not SSL-only mode

4538039

On deinstallation, Oracle Internet Directory entries are not automatically deleted.

Manually delete the entry as follows:

  1. Set the ORACLE_HOME environment variable.

  2. Start the oidadmin tool as follows:

    $ORACLE_HOME/bin/oidadmin

    Note: See Oracle Internet Directory Administrator's Guide for detailed information on using the oidadmin tool.

  3. In the Directory Server Name Manager dialog box, select the directory server you want to connect to, then click OK.

  4. Log on as the orcladmin user.

  5. Search for the cn=OEM entry in the following tree:

    Oracle Internet Directory Servers, orcladmin@host:port, Entry Management, cn=OracleContext, cn=Products, cn=OEM, orclApplicationCommonName=instanceName.host.domain.

  6. Select and delete the entry orclApplicationCommonName=instanceName.host.domain

The Oracle Collaboration Suite Console Application identity for this Applications tier will be deleted from Oracle Internet Directory.

4486439

If ocsdeconfig.sh is not run before using runInstaller to deinstall an Applications tier, the installation program will display a message explaining that you must run a utility to deconfigure the instance. The command in this message is incorrect.

Do not run the given command:

$ORACLE_HOME/perl/bin/perl $ORACLE_HOME/bin/deconfig.pl

Instead, run this command:

$ORACLE_HOME/bin/ocsdeconfig.sh

4518280

The Oracle Contacts Configuration Assistant fails when installing an Applications tier against a non-default Identity Management realm.

Follow the instructions in Section 2.1.2.10, "Installing or Upgrading using non-Oracle Internet Directory Superuser Accounts"

4536195

2.1.4 Globalization Issues in Oracle Collaboration Suite Installation

The following table lists globalization issues in Oracle Collaboration Suite installation and configuration.

Table 2-2 Globalization Issues in Oracle Collaboration Suite Installation

Description Action Bug Number

During installation on Japanese systems, an inconsequential warning message related to the Watanabe font may be given.

Ignore the warning and proceed with the installation.

4478884

If you try to enable a version 10.2 database, the translated error message that appears is inaccurate. It implies that you need version 10.1.0.4.2 or later, when in fact version 10.2 is not supported.

None

4539518

2.1.5 Documentation Issues in Oracle Collaboration Suite Installation

The following sections describe documentation issues for Oracle Collaboration Suite installation.

2.1.5.1 Oracle Content Services Registry Entries for Load Balancing

In step 6 of sections 11.2.8.12, 12.2.8.12, and 13.2.8.12 of Oracle Collaboration Suite Installation Guide, the Oracle Content Services registry entries given are:

  • Oracle Content Services

    dn: cn=FILES,cn=VirtualServices,cn=Files,cn=Services,cn=OracleContext
labeleduri;adminurl
labeleduri;applicationurl
labeleduri;s2swebserviceurl
labeleduri;webdavurl
labeleduri;webservicesurl

However, the entries should be as follows:

  • Oracle Content Services

    dn: cn=Content, cn=VirtualServices,cn=Files,cn=Services,cn=OracleContext
labeleduri;adminurl
labeleduri;s2swebserviceurl
labeleduri;webdavurl
labeleduri;webservicesurl

2.1.5.2 Minimum Value of max_commit_propagation_delay

In Oracle Collaboration Suite Installation Guide, there is an incorrect value in Table 5-1, "Database Configuration Parameters and Their Minimum Values for Installing Oracle Collaboration Suite in an Existing Database". The minimum value for max_commit_propagation_delay is listed as 1, but it should be 0. (4525874)

2.1.5.3 Default Port for Oracle Enterprise Manager Application Server Control

In Appendix F of Oracle Collaboration Suite Installation Guide, Table F-1, "URLs for Components" lists the default port of Oracle Enterprise Manager Application Server Control as 1810. This is incorrect. The default port is 1156. (4526198)

2.2 Oracle Collaboration Suite Upgrade

The following topics describe release note information associated with upgrading Oracle Collaboration Suite.

2.2.1 Known Limitations and Workarounds in Oracle Collaboration Suite Upgrade

The following sections describe known limitations and workarounds for Oracle Collaboration Suite upgrade:

2.2.1.1 Oracle Support Upgrade Articles

Oracle Support has created the following articles on its MetaLink Web site at http://metalink.oracle.com. These articles describe, or will describe, important information and issues you may encounter during Oracle Collaboration Suite upgrade. These articles will be updated regularly by Support personnel and will be based on actual user experiences. Consult them regularly for important updates.

  • Note 330672.1 Known Issues for the Collaboration Suite MRUA (Metadata Repository Upgrade Assistant)

  • Note 315692.1 Restrictions for Oracle Collaboration Suite Upgrades from Oracle Collaboration Suite 9.0.x to Oracle Collaboration Suite 10gR1 (10.1.1)

See Also:

Section 2.1.2.1, "Oracle Support Installation Articles"

2.2.1.2 Applying the Oracle Ultra Search Patch After the Information Storage Database Upgrade

If you are upgrading an Applications tier configured with Oracle Ultra Search, then download patch 4493920 from Oracle MetaLink and apply it to the upgraded Oracle Collaboration Suite Database, according to the instructions contained in the patch ZIP file.

The patch fixes the following issues:

  • The configtool.log file contains the following Oracle Collaboration Suite Upgrade Assistant error message:

    oracle.ocs.upgrade.exception.UpgradeException: Can not migrate data frommetadata repository database to Collaboration Suite database.

  • The wk0create_user.sql script does not grant all necessary privileges.

  • The Oracle Ultra Search Configuration Assistant fails when Oracle Internet Directory is in SSL-Only mode.

  • After the Applications tier upgrade, the Web search does not return results.

If you encounter any of these issues during or after the Applications tier upgrade, then apply the patch to the upgraded Oracle Collaboration Suite Database.

2.2.1.3 Configuring Oracle Workflow for Oracle Content Services

Before configuring Oracle Content Services, configure Oracle Workflow by performing the following steps:

  1. Log in to the Oracle Collaboration Suite Database as a user with appropriate privileges and enter the following command:

    drop user owf_mgr cascade;

  2. From the Oracle Collaboration Suite Applications tier Oracle home, run the following script:

    $ORACLE_HOME/wf/install/wfinstall.csh

    The Oracle Workflow Configuration Assistant starts.

  3. Enter the following parameters in the appropriate fields.

    • Install Option: Select Server Only

    • Workflow Account: Leave the default, owf_mgr.

    • Workflow Password: Provide the same password as the Oracle Content Services schema password.

    • SYS Password: Provide the password for the database user SYS. You must supply this value.

    • TNS Connect Descriptor: Copy this value from the tnsnames.ora file, located in $ORACLE_HOME/network/admin. For example:

      (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myhost.mydomain.com)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=orcl.mydomain.com)))

    Do not select the Enter LDAP Parameters, Enter Mailer Parameters, or Change Tablespace options.

  4. Click Submit.

  5. Proceed with configuring Oracle Content Services using the Oracle Collaboration Suite Control Console.

2.2.1.4 Entering Correct Passwords for Database Schema

Make sure the passwords entered in the Specify Database Schema Passwords dialog box during the Infostore upgrade are correct. They are not being validated and can cause the upgrade to fail if incorrect. (4510605)

2.2.1.5 Upgrading an Oracle Database 10g (10.2) to Oracle Collaboration Suite 10g Release 1 (10.1.1)

If you have already upgraded your Oracle Collaboration Suite Release 2 (9.0.4) information storage database to Oracle Database 10g (10.2), then you cannot upgrade the database to Oracle Collaboration Suite Database 10g Release 1 (10.1.1) or enable the database as an Oracle Collaboration Suite Database.

Support for enabling an Oracle Database 10g (10.2) is planned for Oracle Collaboration Suite 10g Release 1 (10.1.2).

2.2.1.6 Manually Migrating Oracle Ultra Search Index and Configuration Data

These steps are required if you migrated Oracle Ultra Search data using the manual migration scripts. If you want to point your Web search to an instance other than the default WK_INST instance, you should also follow this procedure.

After the Applications tier upgrade, perform the following steps:

  1. In Oracle Internet Directory Service Registry, set the WK_INST instance as the default instance by changing its orclstatus to 'default' and changing the orclstatus of the other entries to the empty string.

  2. Update the oc4j-ra.xml file of the Oracle Ultra Search searchlet to point to the manually migrated instance. In the $ORACLE_HOME/j2ee/OC4J_OCSClient/connectors/UltraSearch/UltraSearch/META-INF/o c4j-ra.xml file, modify the following lines:

    <config-property name="virtualServiceDn" value="<INSTANCE_DN>"/>
<config-property name="connectionURL" value="<JDBC_CONN>"/>
<config-property name="userName" value="<USERNAME>"/>
<config-property name="password" value="<PASSWORD>"/>
<config-property name="instanceName" value="<INST_NAME"/>

    Where:

    • INSTANCE_DN is the Oracle Ultra Search instance's dn string in Oracle Internet Directory

    • JDBC_CONN is the JDBC connection string to the Oracle Ultra Search instance

    • USERNAME is Oracle Ultra Search instance schema name

    • PASSWORD is Oracle Ultra Search instance schema password

    • INSTANCE_NAME is the Oracle Ultra Search instance name

    For example:

    <config-property name="virtualServiceDn" value="cn=store:ocs_inst, cn=VirtualServices,cn=UltraSearch,cn=Services,cn=OracleContext>"/>
<config-property name="connectionURL"                 value="<jdbc:oracle:thin:@stana08:1521:store>"/>
<config-property name="userName" value="<ocs_us>"/>
<config-property name="password" value="<ocs_us>"/>
<config-property name="instanceName" value=="ocs_inst"/>

  3. Delete the cached version of the file in $ORACLE_HOME/j2ee/OC4J_OCSClient/application-deployments/default/UltraSearch/oc4j-ra.xml.

  4. Restart the OC4J_OCSClient instance.

2.2.1.7 Configuring Oracle Collaboration Suite Search with an Enabled Database

After upgrading Oracle Collaboration Suite with an enabled custom database, Oracle Collaboration Suite Search will not return any results (4540079). Correct this problem as follows:

  1. Log in to the Oracle Collaboration Suite Database as wk_test.

  2. Run the following commands:

    exec wk_adm.use_instance('wk_inst');
exec wk_util.register_dft_federated_sources;

  3. Restart the OC4J_OCSClient process using OPMN by entering the following command on the Applications tier:

    $ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=OC4J_OCSClient

2.2.1.8 Granting Oracle Real-Time Collaboration Users BUSINESSADMIN and BUSINESSMONITOR Roles

To grant businessadmin and businessmonitor roles to the users who had them before the upgrade, perform the following steps after the middle tier upgrade:

  1. Log in to the Oracle Collaboration Suite Database used by Oracle Real-Time Collaboration as the rtc_app user. Run the following query to find out which Oracle Real-Time Collaboration users have businessadmin and businessmonitor roles:

    select user_name, CASE WHEN default_role_id IN(6,7) THEN 'businessmonitor'  WHEN default_role_id IN(4,8) THEN 'businessadmin' END "Role Name" from rtc_users where default_role_id in (6,7,4,8);

    For example, if you have a user RTCBADMIN with the businessadmin role and a user RTCBMONITOR with the businessmonitor role, the query returns the following response:

    USER_NAME            Role Name
-------------------- ---------------
RTCBADMIN            businessadmin
RTCBMONITOR          businessmonitor 

2 rows selected.

  2. Grant these users the businessadmin or businessmonitor role by entering the following command from the Oracle Collaboration Suite Applications tier Oracle home imeeting/bin directory:

    rtcctl> modifyRole -username username -rolename {businessadmin|businessmonitor}

    where username is the name of the Oracle Real-Time Collaboration user with businessadmin or businessmonitor privileges before the upgrade. For example:

    rtcctl> modifyRole -username RTCBADMIN -rolename businessadmin

  3. Log in to Oracle Real-Time Collaboration as the user and verify that the correct administrative or monitor tabs are visible.

2.2.1.9 Modifying Upgraded Calendar Accounts Using Delegated Administration Services

After an upgrade, if you try to modify certain user accounts using Delegated Administration services, an error similar to the following can occur:

Error

Post Plugin Errors.
Calendar - oracle.idm.provisioning.plugin.PluginException: Calendar storage cannot be modified. Use the calendar administration tool to move the calendar account from one storage location to another

This generally happens with user accounts that did not exist in Oracle Calendar before the upgrade. (4513293)

There are two workarounds for this problem; both involve changing the status of the account from UPGRADE_IN_PROGRESS to PROVISIONING_NOT_REQUIRED.

Workaround 1: Using the Oracle Directory Manager

  1. Start Oracle Directory Manager:

    $ORACLE_HOME/bin/oidadmin

  2. Log in to Oracle Directory Manager.

  3. In the System Objects frame:

    1. Expand Entry Management.

    2. Navigate to the appropriate subscriber dn, such as dc=com | dc=acme.

    3. Expand cn=users.

  4. Select the affected user.

  5. In the right pane, find the following attribute:

    orclUserApplnProvStatus;CALENDAR_CALENDAR

  6. Set its value to PROVISIONING_NOT_REQUIRED.

Workaround 2: Using the command line

Run the following command:

% printf "dn: `$ORACLE_HOME/bin/ldapsearch -host host -port port -D managerdn -w password -b basedn (mail=mail_of_the_user) dontremoveme`\nchangetype: modify\nreplace: orclUserApplnProvStatus;CALENDAR_CALENDAR\norclUserApplnProvStatus;CALENDAR_CALENDAR: PROVISIONING_NOT_REQUIRED\n" | $ORACLE_HOME/bin/ldapmodify -host host -port port -D managerdn -w password

For example:

% printf "dn: `$ORACLE_HOME/bin/ldapsearch -host host1.acme.com -p 389 -D cn=orcladmin -w test1 -b dc=acme,dc=com (mail=john.doe@acme.com) dontremoveme`\nchangetype: modify\nreplace: orclUserApplnProvStatus;CALENDAR_CALENDAR\norclUserApplnProvStatus;CALENDAR_CALENDAR: PROVISIONING_NOT_REQUIRED\n" | $ORACLE_HOME/bin/ldapmodify -host host1.acme.com -p 389 -D cn=orcladmin -w test1

2.2.1.10 Application Server Metadata Repository Upgrade Assistant

The Application Server Metadata Repository Upgrade Assistant is not currently part of the Oracle Collaboration Suite media kit. Customers needing this should see Note 330672.1 on Oracle MetaLink at:

http://metalink.oracle.com

2.2.1.11 Applications Tier Upgrade Fails When orclMailSMTPExternalFilterProcess is not Null

The Applications tier upgrade fails when orclMailSMTPExternalFilterProcess is not null. If this attribute is set prior to upgrade, then it must be cleared out and re-set after the upgrade by peforming the following:

  1. In Oracle Internet Directory unset orclMailSMTPExternalFilterProcess. This is located under cn=OracleContext->cn=Computers->cn=<mid_host>->cn=<mid_name>->cn=EmailServer->cn=mailProcesConfig->cn=<mid_host>:UM_SYSTEM:smtp_out:orclMailSMTPExternalFilterProcess.

  2. Create an LDIF file with the following two entries (dn: cn=... should be on the same line):

    dn: cn=<upgrade_oracle_home_path>,cn=<hostname>,cn=Computers,cn=OracleContext changetype: modrdn newrdn: cn=<old_oracle_home_dir_name(not fullpath)> . dn: cn=EMailServerContainer,cn=Products, cn=OracleContext changetype: modifyreplace: orclproductversionorclproductversion: 9.0.4

  3. Run the following and then click the Retry button:

    $ORACLE_HOME/bin/ldapmodify -h stanc01 -p 4032 -D cn=orcladmin -w welcome1 -c -v -f <ldif_filename_for_above>

2.2.1.12 Calendar Resource Browsing Right is not Created in an Upgrade Scenario

The Calendar resource browsing right is not created in an upgrade scenario (4507691). In addition, in an upgrade scenario, Oracle Workspaces does not have sufficient permissions to list Calendar resources. To correct these problems, apply the following LDIF:

  1. Run the following command to apply the LDIF:

    ldapmodify -h hostname -p port -D binddn -w passwd -f file

  2. Apply the LDIF as follows:

    dn: cn=Resources,cn=Calendar,cn=Products,cn=OracleContext,<subscriber dn> changetype: modify add: orclaci orclaci: access to entry filter=(objectclass=orclCalendarResource) by dn=".*,cn=Application Entities,cn=Calendar,cn=Products,cn=OracleContext" (browse,add,delete) by * BindMode="Proxy" (browse,noadd,nodelete) - add: orclaci @ orclaci: access to attr!=(userpassword, @ authpassword,orclpassword,orclPasswordAttribute) by dn=".*,cn=Application Entities,cn=Calendar,cn=Products,cn=OracleContext" (read,search,compare,write,selfwrite) by * BindMode="Proxy" (read,search,compare)

2.2.2 Known Issues in Oracle Collaboration Suite Upgrade

The following table lists known issues in Oracle Collaboration Suite upgrade.

Table 2-3 Known Issues in Oracle Collaboration Suite Upgrade

Description Action Bug Number

During an upgrade, you are informed that an orclguest user account will be created and you are asked to enter a password for it. However, if an orclguest user account exists in the version being upgraded, the password you enter is ignored and the existing account is simply migrated.

If an orclguest user account exists in the version being upgraded, just enter a false password when prompted. The password you enter will be ignored, and the original account information (including its password) will be migrated.

4634919

When upgrading standalone Oracle Calendar application system installations, the upgrade assistant does not accept the destdir and destver parameters.

Do not use the destdir and destver parameters—they are not needed in 10g Release 1 (10.1.1). For example:

/u01/ocs10/ocas/upgrade/ocasua.sh
-srcver 9.0.4
-srcdir /u01/ocs904
-confdir /usr/local/apache/conf

4473874

When upgrading an Applications tier configured with Oracle Ultra Search, there are errors during and after the upgrade.

After upgrading the Oracle Collaboration Suite information storage database, download patch 4493920 from Oracle MetaLink and apply it to the upgraded Oracle Collaboration Suite Database, according to the instructions contained in the patch ZIP file.

This patch addresses the issues listed in Section 2.2.1.2.

4493920

After upgrading an Applications tier configured with Oracle Mail to 10.1.1, there is a NullPointerException after logging into the Oracle WebMail page at http://apptier_host:apptier_port/um.

On the system running the upgraded Applications tier, perform the following steps where $ORACLE_HOME is the upgraded Applications tier Oracle home:

  1. Append the contents of the $ORACLE_HOME/um/client/config/toolkit.properties to the contents of $ORACLE_HOME/j2ee/OC4J_OCSClient/config/oc4j.properties. For example:

    cat $ORACLE_HOME/um/client/config/toolkit.properties >>$ORACLE_HOME/j2ee/OC4J_OCSClient/config/oc4j.properties

  2. Set the PERL5LIB environment parameter to:

    $ORACLE_ HOME/perl/lib:$ORACLE_HOME/perl/lib/5.6.1:$ORACLE_HOME/perl/lib/site_ perl/5.6.1

  3. Execute the clientupgv2_1.pl script:

    $ORACLE_HOME/perl/bin/perl $ORACLE_HOME/oes/bin/clientupgv2_1.pl -o path_to_old_oracle_home -n path_to_new_oracle_home

  4. Restart the OC4J_OCSClient container:

    $ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=OC4J_OCSClient

4513034, 4526818, 4540048

Passwords entered in the Specify Database Schema Passwords dialog box are not being validated and can cause the upgrade to fail if incorrect.

Be sure to enter the correct passwords in the Specify Database Schema Passwords dialog box. This issue is also documented in Section 2.2.1.4, "Entering Correct Passwords for Database Schema".

4510605

If you performed the procedures to manually migrate the Oracle Ultra Search index and configuration data and you created a new schema with a different password than the original schema, then the password in the data-sources.xml file is out-of-date.

Open the j2ee/OC4J_OCSADMIN/config/data-sources.xml file in the upgraded Applications tier Oracle home and change the password value to the new password.

4513620

When you choose to use the existing Oracle Ultra Search index during the Applications tier upgrade, the upgraded Oracle Collaboration Suite Search uses the existing index and returns search results, but the Query application does not return any results.

When you choose to use the existing index, you can perform searches right away using Oracle Collaboration Suite Search. However, you cannot perform searches right away using the Query application at http://host:port/ultrasearch/query/search.jsp. This is because this application points to the new system and searches will not return correct results until the crawling is completed.

To verify that the crawling is complete:

  1. Access the administrator page at

    http://host:port/ultrasearch/admin

  2. Select the instance and click the Schedules tab.

  3. Check every schedule to see if the crawling has completed.

4513123

After upgrading the Applications tier and trying to configure Oracle Content Services, there is an error:

The database you have chosen does not contain valid Workflow schema. Choose another database to proceed.

Follow the steps described in Section 2.2.1.3

4514251

After manually migrating the Oracle Ultra Search index and configuration data and upgrading the Applications tier, the Oracle Collaboration Suite Search page cannot perform searches.

This problem can occur if you migrated an Oracle Ultra Search instance other than the default WK_INST instance. To fix it, after the Applications tier upgrade, perform the steps in Section 2.2.1.6.

4519770

On most platforms, the path for sockets used by FastCGI is limited to 108 characters. If your path exceeds this length, you may see the following error during the Oracle HTTP Server upgrade:

FastCgiServer ORACLE_ HOME/Apache/Apache/fcgi-bin/echo: path "ORACLE_HOME/Apache/Apache/logs/fastcgi/2c62973500753dd86979136f0c55618a" is too long for a Domain socket.

Before starting the middle tier upgrade, add the following line to the FastCGI module configuration section in httpd.conf file located in the source Oracle home's Apache/Apache/conf directory:

FastCgiIpcDir "/tmp/fcgi"

For example,

<IfModule mod_fastcgi.c>
FastCgiIpcDir "/tmp/fcgi"
Alias /fastcgi/ "/usr/local/home/ocssgt/ocsv2midupm15cd2_  zhtw/OraHome1/Apache/fastcgi/"
...
</IfModule>

4519543

Single Sign-On fails with Mozilla/Firefox-based browsers after performing an upgrade

To work around this issue, either:

  • Use Microsoft Internet Explorer to log in to applications

  • Manually change the URL in the address field when you get the error. (The user will be able to login to Single Sign-On. It is only in the redirect step that the error occurs. At this point, the user can manually change the port number of the address field to access the application.) Perform the following steps:

    1. Enter the URL to access an application, such as http://host:7777/search to access Oracle Collaboration Suite Search.

    2. The browser is redirected to the Single Sign-On page. Enter user name and password to log in.

    3. An error page is shown.

    4. Manually edit the URL in the address field back to port 7777. The application is now displayed correctly.

4541079

The upgrade of a middle tier configured with Oracle Real-Time Collaboration does not preserve the businessadmin and businessmonitor roles. Users who were granted these roles before the upgrade are not able to see the administrative or monitor tabs after the upgrade.

After the middle tier upgrade, perform the steps described in Section 2.2.1.8.

4477138

After the upgrade from Oracle Collaboration Suite Release 1 (9.0.3.1), when some users log into the Oracle Collaboration Suite portal page at:

http://hostname:port/pls/portal

all the portlets display errors.

This error occurs for the orclguest user or for any user whose default portal page was changed. When logging in to the portal, the user is redirected to the old portal page rather than the new Oracle Collaboration Suite Collaborative Portlets page.

To set the user's default home page to the new portal, perform the following steps:

  1. Go to the Oracle Collaboration Suite portal page and log in as orcladmin.

  2. Select the Builder link.

  3. Click the Administer tab.

  4. In the Portal User Profile portlet, enter orclguest, then click Edit.

  5. On the Default Home Page field, click Reset.

  6. Click OK.

When logging into the portal page, the user is directed to the new page.

4518896

In certain cases, the Ultrasearch Configuration Assistant may fail during an upgrade. The error given looks similar to the following:

Failed to create service entries for existing Ultra Search instances
java.sql.SQLException: ORA-20000: Oracle Ultra Search error
ORA-06512: at "WKSYS.WK_ERR", line 179
ORA-06512: at line 1

This may happen if the targetDN catalog was created in Oracle Internet Directory using an Oracle Collaboration Suite tool or a manual workaround. In this case, during the upgrade, the command to create the targetDN fails, and catalogs for other components are also not created.

Workaround:

  1. Before upgrading Oracle Internet Directory, remove the targetDN catalog (with catalog.sh).

    $ORACLE_HOME/ldap/bin/catalog.sh -connect connect_descriptor  -delete -attr targetDN

    where connect_string is the database connect string for the Infrastructure database, such as asdb.

  2. After the Oracle Internet Directory upgrade, recreate the targetDN catalog with catalog.sh. This will populate the existing targetDN values to the catalog.

    $ORACLE_HOME/ldap/bin/catalog.sh -connect connect_string  -delete -attr targetDN
$ORACLE_HOME/ldap/bin/catalog.sh -connect connect_string  -add -attr targetDN

If you do not perform the preupgrade step and run into problems during the upgrade, Oracle recommends that you restore the preupgrade Infrastructure and other Oracle Collaboration Suite components from backup, perform the preupgrade step in this section and start the upgrade again.

4534141

After upgrading the middle tier, Web searches using Oracle Collaboration Suite Search do not return any results.

If you did not select the option to use the existing index, then after the middle tier upgrade, modify the oc4j-ra.xml file so that Oracle Collaboration Suite Search points to the index in the upgraded Oracle Collaboration Suite Database.

Perform the following steps on the system running the upgraded Applications tier.

  1. Modify the $ORACLE_HOME/j2ee/OC4J_OCSClient/connectors/UltraSearch/UltraSearch/META-INF/oc4j-ra.xml file by entering the user name, password and instance name of the Oracle Ultra Search instance that contains the index documents:

    For example:

    <config-property name="userName" value="wk_test"/>
<config-property name="password" value="wk_test"/>
<config-property name="instanceName" value="wk_inst"/>

  2. Remove the cached version of the oc4j-ra.xml file located in the $ORACLE_HOME/j2ee/OC4J_OCSClient/application-deployments/default/UltraSearch directory.

  3. Restart the OC4J_OCSClient instance:

    $ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=OC4J_OCSClient

4520407

The migration of the Oracle Ultra Search instance during the middle tier upgrade does not migrate the List of Values (LOV) for a search attribute.

If you have defined a search attribute before the upgrade, then the search attribute is migrated to the new instance but not its List of Values. For example, before the upgrade, there is a 'developer' search attribute with list of values 'MTS','SMTS','PMTS', and 'CMTS'. The upgrade process only migrates the 'developer' search attribute.

The workaround is to re-create the list of values for each search attribute in the new instance.

4547755/4546079

After upgrading Oracle Collaboration Suite and enabling a custom database, Oracle Collaboration Suite Search may not work.

See Section 2.2.1.7, "Configuring Oracle Collaboration Suite Search with an Enabled Database".

4540079

The permission to browse Calendar resources is not granted during an upgrade.

To correct the problem, create and apply an LDIF file with the following text:

dn: cn=Resources,cn=Calendar,cn=Products,cn=OracleContext,<subscriber dn>changetype: modifyadd: orclaciorclaci: access to entry filter=(objectclass=orclCalendarResource)  bydn=".*,cn=Application Entities,cn=Calendar,cn=Products,cn=OracleContext"(browse,add,delete) by * BindMode="Proxy" (browse,noadd,nodelete)-add: orclaci@ orclaci: access to attr!=(userpassword,@ authpassword,orclpassword,orclPasswordAttribute)  by dn=".*,cn=ApplicationEntities,cn=Calendar,cn=Products,cn=OracleContext"(read,search,compare,write,selfwrite) by * BindMode="Proxy"(read,search,compare)

4560542/4514433

2.2.3 Globalization Issues in Oracle Collaboration Suite Upgrade

The following table lists globalization issues when upgrading Oracle Collaboration Suite.

Table 2-4 Globalization Issues in Oracle Collaboration Suite Upgrade

Description Action Bug Number

When upgrading, if Ultrasearch contains a multiple-byte schema name and multiple-byte instance name, manual workaround steps are needed.

If you cannot enter a multiple-byte schema name in Oracle Universal Installer, create an English schema in 10.1.1 to which to migrate the Ultrasearch instance and index data. For a multiple-byte instance name, manually modify the upgrade response file with the instance name encoded in Java \uxxxx format.

4484553

When upgrading to Oracle Real-Time Collaboration 10g Release 1 (10.1.1), the schema password supplied must be the RTC_APP schema password and all Oracle Real-Time Collaboration schema passwords (RTC, RTC_REP, RTC_IM, and RTC_APP) get reset to the supplied password.

The workaround is to change the RTC_APP schema password to be the same as the RTC schema password before upgrading.

4400972

2.2.4 Documentation Issues in Oracle Collaboration Suite Upgrade

The following table lists documentation issues in Oracle Collaboration Suite Upgrade Guide.

Table 2-5 Documentation Issues in Oracle Collaboration Suite Upgrade

Description Action Bug Number

The instructions in Section 5.3.1.2, "Execute wk0config.sql for Oracle Ultra Search" of the Oracle Collaboration Suite Upgrade Guide contain an error.

Step 3 of this section should be:

$ORACLE_HOME/bin/sqlplus "sys/sys_password as sysdba"

where sys_password is the password for sys.

4527038

Sections 1.5.2.3, "Distributed Oracle9iAS Metadata Repository," and 7.1.2, "Upgrading a Distributed Oracle9iAS Metadata Repository" of Oracle Collaboration Suite Upgrade Guide contain incorrect information.

These sections incorrectly state that if you have a distributed Oracle9iAS Metadata Repository, then you can upgrade the middle tier before upgrading the Infrastructure configured with the Oracle9iAS Metadata Repository. However, if the database hosting the Oracle9iAS Metadata Repository is not yet upgraded to Oracle Database 10g, then the Oracle Ultra Search upgrade fails when migrating Oracle Ultra Search instance data during the middle tier upgrade.

You must upgrade the Infrastructure configured with the Oracle9iAS Metadata Repository before performing the middle tier upgrade.

4527187

Section 1.5.4.5, "Upgrading Oracle Ultra Search" of Oracle Collaboration Suite Upgrade Guide contains incorrect information.

This section incorrectly states that Oracle Ultra Search supports staged upgrades if there is a distributed Oracle9iAS Metadata Repository.

In a distributed Oracle9iAS Metadata Repository configuration, when the Oracle9iAS Metadata Repository database is upgraded as part of the Oracle9iAS Infrastructure upgrade, Oracle Ultra Search no longer works until the middle tiers are upgraded.

4527187

The steps in Section 6.6.4.4, "Upgrading the Text Index" should be performed after the upgrade of the information storage database.

It is preferable to perform the steps described in this section after the upgrade of the information storage database. Performing them after the middle tier upgrade does not cause any problems, but they only need to be performed once.

Perform the steps whenever the text index is not empty. Determine whether the text index is empty using one of the following methods.

Before the upgrade, log in to the information storage database as the es_mail user and run the following query:

select count(1) from es_imt_msgbody;

If the result is greater than 0, then the index is not empty.

Alternatively, after the upgrade, check the log file ORACLE_HOME/oes/log/upgrade905.log for the following message:

Text search index is not empty.Please upgrade index manually by running  recreate_text_index.sql

4540058

Section 4.5.3, "Preparing for the Oracle Email Upgrade" is missing a step.

Before running the catalog.sh script, set the ORACLE_HOME environment variable to the upgraded Infrastructure Oracle home. If this variable is not set, when you run the script the following error displays:

./catalog.sh: line 24: cd: /ldap/load: No such file or directory
./catalog.sh: line 695: /ldap/log/nullct: No such file or directory
Unable to detect database using connect descriptor iasdb.
Check Net8 client connect descriptor configuration settings.

4539928

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Master Index
Master Index		 Go to Feedback page
Contact Us