Skip Headers
Oracle® Collaboration Suite Release Notes
10g Release 1 (10.1.2) for Linux
Part Number B25475-23
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

3 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 February 23, 2007. Additional updates and new information can be found in Note 415183.1 on http://metalink.oracle.com.

3.1 Oracle Collaboration Suite Installation

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

3.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. 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.

3.1.2 Resolved Issues in Oracle Collaboration Suite Installation

Table 3-1 lists resolved issues in Oracle Collaboration Suite installation.

Table 3-1 Resolved Issues in Oracle Collaboration Suite Installation

Description Resolved In Bug Number

Although the Oracle Web Access client Configuration Assistant appeared to work, it was possible that no corresponding schema was created in the database; selecting the latter during an Applications tier install could result in the following error:

Error:*** Alert: Error connecting to the datbase that you have selected for Oracle Collaboration Suite Web Access.
Please make sure that the database is up and running and the ICSYS user account is unlocked or select another database.

10.1.2

4540338

In a custom installation, if Enterprise Manager was not installed, the Oracle Web Access client Configuration Assistant would not run correctly and could display the following error:

Web Access Configuration Assistant failed;

Exception in thread main java.lang.noClassDefFoundError:
oracle/sysman/emSDK/conf/TargetDeletionException:

10.1.2

4547739

3.1.3 Known Limitations and Workarounds in Oracle Collaboration Suite Installation

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

3.1.3.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 339831.1 List Of Patches To Install On Top Of Collaboration Suite 10.1.2: Lists recommended Oracle Collaboration Suite patches.

  • Note 339832.1 Additional Hints How To Install Collaboration Suite 10.1.2: Provides additional hints for installation.

  • Note 361948.1 How to resolve issues due to applying DB PSR 10.1.0.5 over Oracle Collaboration Suite: Addresses a specific issue and workaround related to the application of Oracle Database Patch Set Release 10.1.0.5 over installations of Oracle Collaboration Suite 10.1.2.


See Also:

For the latest notes from Oracle Support and links to all Oracle Collaboration Suite documentation libraries, see note 386616.1 at http://metalink.oracle.com.

3.1.3.2 Database Versions

Oracle Collaboration Suite 10g 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.

Oracle recommends that customers upgrade Oracle Database 10.1.0.4.2 to version 10.1.0.5. Version 10.1.0.5 can be obtained by downloading patch 4505133 from http://metalink.oracle.com.

Customers wishing to use their own existing database must upgrade that database to at least version 10.1.0.5 before using the "Enable Customer Database" option from the Installer.

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 (or advised) to upgrade databases used by Oracle Collaboration Suite 10g to 10.2 when that version is made available for different platforms. Oracle recommends upgrading to 10.2 after installing Oracle Collaboration Suite, not before. For helpful information on upgrading your database, see the following notes on Oracle's MetaLink Web site at http://metalink.oracle.com.

  • Note 306705.1 Internal Error Message 684 Could Not Be Found In The Msb File 684

  • Note 361948.1 How to resolve issues due to applying DB PSR 10.1.0.5 over Oracle Collaboration Suite

For further information on Oracle Collaboration Suite certified components, see Oracle Collaboration Suite Certification Guide.

3.1.3.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.

3.1.3.4 Upgrading the Oracle Collaboration Suite Database to RDBMS 10.2.0.x Requires Post-upgrade Steps for Ultra Search

When upgrading to RDBMS, the following error message will appear:

The following components cannot be upgraded as the
corresponding upgrade scripts are missing:
Oracle Ultra Search ($ORACLE_HOME/ultrasearch/admin/wkdbmig.sql)

If you want to upgrade these components, you must first install
them, using the OUI and then re-run the Upgrade Assistant.
Do you want to continue with the upgrade?

Note: If you continue, the above components will not be consideredas part of the upgrade process.

                                                      Yes | No

To work around this problem, do the following:

  1. Click Yes to continue with the upgrade.

    In Oracle Database 10g Release 2 (10.2), Ultra Search was moved to the Companion CD. To upgrade Oracle Collaboration Suite Ultra Search, you must complete the Oracle Database 10g products installation from the Companion CD after the database upgrade to RDBMS 10.2 as described in the remaining steps.

  2. Install Ultra Search from the Companion CD to the same new RDBMS 10.2 ORACLE_HOME.

  3. Shut down the database and then start it up in upgrade mode (startup upgrade). If this is a Real Application Clusters database, start it in exclusive mode (cluster_database=false).

  4. In SQL*Plus, execute the Ultra Search upgrade script, ORACLE_HOME/ultrasearch/admin/wkdbmig.sql.

  5. Restart the database in normal mode.

3.1.3.5 Required Steps for Setting Up Oracle Content Services Against a Newly Installed Database

If you run the Enable Customers Oracle Collaboration Suite Database install option on top of your external database, or OCSDbScehmaReg.sh against your external database, be aware that only the Content schema is created. Before configuring Oracle Content Services from the Applications tier, a workflow schema needs to be created in the database. Depending on the version of your database, the following steps must be performed during Applications tier installation.

If your database version is 10.1.0.4+, and if you have not run the Metadata Repository Creation Assistant against this database:

If your database Version is 10.2.0.+:

3.1.3.6 Content Services Configuration Assistant Failure on Single Box Install

Invoking a new shell from .cshrc/.bashrc/.zshrc (depending on your shell) causes the Applications tier Oracle Content Services configuration assistant to hang.

Workaround

Make sure you do not have any commands to invoke a new shell in your .cshrc/.bashrc/.zshrc files. If your Applications tier configuration assistant appears to be hanging at the UploadAgentDefinitions action for a long time, check the .cshrc file in your environment, delete any commands invoking a new shell, then retry Oracle Content Services configuration.

3.1.3.7 Oracle Portal Requires Oracle Knowledge Base Component

If you choose to install your own RDBMS 10.1.0.2.0 (+ 10.1.0.5 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 3.1.3.16, "Application Server Metadata Repository Creation Assistant"

3.1.3.8 Correcting Oracle Messenger Sign-In Failure in High Availability Environments

If you are unable to sign in to Oracle Messenger in a Single Cluster high availability, collocated Identity Management high availability, or distributed Identity Management 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.

3.1.3.9 Oracle Enterprise Manager Grid Control Versions

To manage Oracle Collaboration Suite 10g Release 1 (10.1.2), 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/

3.1.3.10 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:

3.1.3.10.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
3.1.3.10.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
3.1.3.10.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.

3.1.3.10.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"

3.1.3.11 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)

3.1.3.12 Unnecessary root.sh Script in Oracle Calendar Standalone Installation

When installing Oracle Calendar standalone, the following prompt opens:

Alert: A configuration script needs to be run as root before installation window open, open another window and run $ORACLE_HOME/root.sh as root, then return to this window and click OK to continue.

Ignore this prompt and do not run root.sh—it is not necessary. Click OK and continue with the installation. (4539503)

3.1.3.13 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

3.1.3.14 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.

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>

3.1.3.15 Unstable Database Instances in Linux RAC Database with NAS

In SLES9 and Red Hat 4.0, if you choose to have Oracle Collaboration Suite Real Application Clusters (RAC) Database with file storage as NAS, the database instances may not be stable (4529718).

To work around this issue, when Oracle Universal Installer prompts you to run root.sh, do the following:

  1. cd ORACLE_HOME/assistants/dbca/templates

  2. cp -p Collaboration_Suite_InfoStore.dbc Collaboration_Suite_InfoStore.dbc.ORG

  3. open the file Collaboration_Suite_InfoStore.dbc and add the following line in to the <InitParams> section:

    <initParam name="filesystemio_options" value="directIO"/>

  4. Repeat steps 1 through 3 for every node in the cluster

  5. Run root.sh and then continue with the installation

3.1.3.16 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

3.1.3.17 Installing a Stand-Alone Oracle Calendar Applications Tier on Red Hat Linux 4.0

Attempting to install a stand-alone Oracle Calendar 10g (10.1.2) instance on Red Hat Linux 4.0 platforms will fail with the following message (Bug 4561453):

Checking operating system version: must be SuSE-7, redhat-2.1AS, redhat-2.1, UnitedLinux-1.0, redhat-3, SuSE-8 or SuSE-9
Failed <<<<

To work around this issue, follow these steps:

  1. Copy the 10.1.2_Linux_DVD/calendar_standalone/install/oraparam.ini file to a local location

  2. Locate the following line:

    Linux=SuSE-7,redhat-2.1AS,redhat-2.1,UnitedLinux-1.0,redhat-3,SuSE-8,SuSE-9

  3. Add "redhat-4," to the list of supported platforms, and then save the file.

  4. Launch the standalone Oracle Calendar installer by using the following command:

    runInstaller -paramFile <path-to-local-oraparam.ini>

    Where <path-to-local-oraparam.ini> is the path to the saved file you created in the previous steps.

3.1.3.18 Applications Tier Service-to-Service Operations Require a Dedicated Load Balancer Virtual server

A problem with the digest login module (4650986) prevents Oracle Collaboration Suite deployment scenarios using multiple Applications tiers accessed using a load balancer virtual server from working properly. The digest login module issue only occurs in Oracle Collaboration Suite service-to-service operations, when one Oracle Collaboration Suite Application performs a service request against another Oracle Collaboration Suite Application.

This includes deployment scenarios described in ÒConfiguring the First Oracle Collaboration Suite 10g Applications Tier with a Load BalancerÓ and ÒInstalling Subsequent Instance of Oracle Collaboration Suite 10g ApplicationsÓ sections of the Oracle Collaboration Suite Install Guides.

In this type of installation, multiple Java Virtual Machines (JVMs) are used because Oracle Collaboration Suite Applications tier access may be routed to any one of the Applications tiers by the load balancer. If you are using the service-to-service features of Oracle Collaboration Suite Applications in a multiple Oracle Collaboration Suite Applications tier deployment (these features enable integration between different Oracle Collaboration Suite applications) then you may see errors like the following in a component's application log:

$ORACLE_HOME/j2ee/OC4J_Portal/application-deployments/ocsprovs/OC4J_Portal_default_island_1/application.log ,
caused by: [SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported
response content type "text/html", must be: "text/xml".
Response was:
<HTML><HEAD><TITLE>401
Unauthorized</TITLE></HEAD><BODY><H1>401
Unauthorized</H1></BODY></HTML>

These problems occur with several applications, including various Oracle Collaboration Suite Portal portlets, Oracle Workspaces integration with Oracle Content Services, and Oracle Collaboration Suite Search. Applications tier access will fail intermittently for these services.

Workaround

You can use a hardware configuration that will prevent these issues from occurring, while maintaining high-availability. To work around the problem, use a load balancer virtual server that has persistence based routing to the HTTP servers. In this scenario, a single JVM is used, but the services end-point is still load balanced across all the Applications tiers and is not a single point of failure.

With this workaround the Oracle Collaboration Suite Applications service-to-service authentication traffic flows through the persistence-based load balancer virtual server and then goes directly to the Oracle HTTP Server tier. Once authentication is completed, the rest of the application's regular traffic continues to be routed through the clustered Web cache tier.

In conjunction with the new load balancer virtual server, the Oracle Internet Directory Service Registry entries for the Oracle Collaboration Suite Applications Web services URIs are changed to direct to the new load balancer virtual server. The rest of the Service Registry URIs remain the same.

To solve this problem, you must set up a new load balancer virtual server, modify the Oracle Internet Directory Service Registry to use the new virtual server, and then restart the Applications tier, as described in the following steps.

Set up the load balancer as follows:

  1. Create a new virtual server in the load balancer, such as lbr.yourdomain.com:80.

  2. Map the virtual server, ocs_apps_s2s.visioncorp.com:80, to a node pool comprised of:

    • n1:port

    • n2:port

    Where port is the Oracle HTTP Server Listener port. Provided you have not changed it since installation, the port is listed in:

    $ORACLE_HOME/install/portlist.ini

  3. Set Insert Active Cookie persistence for this node pool.

Modify the Oracle Internet Directory Service Registry to use the new virtual server as follows:

  1. Start Oracle Directory Manager and log in to Oracle Internet Directory.


    Note:

    For detailed instructions on using Oracle Directory Manager to modify the Oracle Internet Directory Service Registry, see "Using Oracle Directory Manager to Edit the Oracle Internet Directory Service Registry" in Chapter 7 of Oracle Collaboration Suite Administrator's Guide.

  2. Navigate to Entry Management, OracleContext, then Services.

  3. Under Calendar, make the following changes:

    1. Navigate to:

      cn=OCAS_xxxxx,cn=VirtualServices,cn=Calendar,cn=Services,cn=OracleContext

    2. Select labeleduri;webserviceurl.

    3. Set labeleduri;webserviceurl to:

      http://ocs_apps_s2s.visioncorp.com/ocws-bin/ocas.fcgi

  4. Under Email, make the following changes:

    1. Navigate to:

      cn=webservice,cn=VirtualServices,cn=Email,cn=Services,cn=OracleContext

    2. Select labeleduri;webservice.

    3. Set labeleduri;webservice to:

      http://ocs_apps_s2s.visioncorp.com/oes/ws

  5. Under Content Services, make the following changes:

    1. Navigate to:

      cn=Content,cn=VirtualServices,cn=Files,cn=Services,cn=OracleContext

    2. Select labeleduri;s2sauthenticationurl.

    3. Set labeleduri;s2sauthenticationurl to:

      http://ocs_apps_s2s.visioncorp.com/content/s2s

    4. Select labeleduri;webserviceurl.

    5. Set labeleduri;webserviceurl to:

      http://ocs_apps_s2s.visioncorp.com/content/ws

    6. Select labeleduri;webdavurl.

    7. Set labeleduri;webdavurl to:

      http://ocs_apps_s2s.visioncorp.com/content/dav

  6. Under Real-Time Collaboration, make the following changes:

    1. Navigate to:

      cn=RTC,cn=VirtualServices,cn=RTC,cn=Services,cn=OracleContext

    2. Select labeleduri;integrationserviceurl.

    3. Set labeleduri;integrationserviceurl to:

      http://ocs_apps_s2s.visioncorp.com/imtapp/OracleRTCService

  7. Under Mobile / Wireless, make the following changes:

    1. Navigate to:

      cn=WIRELESS1,cn=VirtualServices,cn=Wireless,cn=Services,cn=OracleContext

    2. Select labeleduri:presencewebserviceurl.

    3. Set labeleduri:presencewebserviceurl to:

      http://ocs_apps_s2s.visioncorp.com/presence/webservices

After setting up the load balancer and modifying the Oracle Internet Directory Service Registry, restart the Oracle Collaboration Suite Applications tiers.

3.1.3.19 Globalization Shortcut Keys for Oracle Content Services

If Oracle Content Services is installed in languages other than English, the characters e and s are mapped to the Delete key when using the Web interface. Because of this, pressing e or s in some circumstances can cause a selection to be deleted. (4716518)

Workaround: During the Applications tier installation, start opmn and switch to English locale before running the opmn commands; for example, if the locale is set to French (fr_FR.UTF-8):

  1. Start the Applications tier opmn:

    opmnctl start

  2. Change the locale to English (en_US.UTF-8).

  3. Run the opmn commands:

    opmnctl startproc ias-component=HTTP_Server
opmnctl startproc ias-component=WebCache
opmnctl startproc ias-component=Content

3.1.3.20 Do Not Use Oracle Application Server Patch Set 10.1.2.1

If you perform a fresh installation of Oracle Collaboration Suite 10g Release 1 (10.1.2), or upgrade to Oracle Collaboration Suite 10g Release 1 (10.1.2) from version 9.0.x, do not apply the Oracle Application Server 10.1.2.1 Patch Set.

The only circumstance under which you should apply the Oracle Application Server 10.1.2.1 Patch Set is after patching an Oracle Collaboration Suite 10.1.1 installation with the Oracle Collaboration Suite 10.1.2 Patch Set.


See Also:

  • The section "Can I Update An Existing Oracle Collaboration Suite Release 10.1.1.0.2 Installation to Oracle Collaboration Suite Release 10.1.2?" in Chapter 6 of Oracle Collaboration Suite Installation Guide.

  • The section "Upgrading from Oracle Collaboration Suite Release 10.1.1.0.2" in Chapter 7 of Oracle Collaboration Suite Installation Guide.

  • The README.html file included with the Oracle Collaboration Suite 10.1.2 Patch Set. This file contains installation instructions and describes issues specific to the 10.1.2 Patch Set. To get the Patch Set (and its README), navigate to http://metalink.oracle.com and download patch 4713160.

3.1.3.21 Deinstalling or Removing an Oracle Enterprise Manager 10g Grid Control Console 10.1.0.2 Management Agent on a Computer with Oracle Application Server 10g (9.0.4)

If you installed the Enterprise Manager Grid Control 10.1.0.2 Management Agent on a computer which has one or more instances of Oracle Application Server 10g (Release 9.0.4) or Oracle Collaboration Suite, you must take certain actions to safely deinstall or remove the Management Agent.

If Oracle Application Server 10g was installed prior to the Management Agent, it will have been automatically discovered during the Management Agent installation and configuration phase. When you use the Grid Control Console, you should see the application server instance listed as a set of targets on the host where the Oracle Management Agent resides.

In addition, if you explicitly configured Central Management from the Application Server Control Console, or if you discovered the Oracle Application Server 10g instance by clicking the Add button on the Grid Control Console Application Servers subtab, you will need to follow these instructions if you want to remove the Oracle Management Agent:

  1. Before removing the Oracle Management Agent, remove the Oracle Application Server 10g instance from Grid Control Console as follows:

    1. In the Grid Control Console, select Targets, then Applications Servers.

    2. Select the instance that you want to remove, and click Remove.

    3. Confirm your action, and wait for the operation to complete.


      Note:

      You should wait for all the subtargets of the application server instance to be removed as well. You can check on the progress of this asynchronous operation by clicking Deleted Targets on the Management Services tab. Wait for all the targets pending deletion to be removed.

  2. Once this operation is done for each Oracle Application Server 10g instance on the host, you can then remove the Oracle Management Agent.

If you have already removed the Management Agent (through deinstallation or otherwise), remove the AGENT_HOME entry from the centralagents.lst file from the AS_HOME/sysman/emd directory. If AGENT_HOME is the last entry, you can delete the centralagents.lst file. You must do this for each Oracle Application Server 10g instance. If you do not follow these steps, you may encounter errors when modifying your Oracle Application Server 10g configuration; for example, when creating or removing OC4J instances.

3.1.4 Known Issues in Oracle Collaboration Suite Installation

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

Table 3-2 Known Issues in Oracle Collaboration Suite Installation

Description Action Bug Number

If you plan to use Automated Storage Management (ASM), and mark your disks with Linux ASMLib, the Oracle Database installer will not be able to discover your disks.

Do a software-only installation and then use the Database Configuration Assistant (DBCA) to create your database (or do a custom installation).

3386190

Since Verify Filters are not available on Linux on Power, Oracle Content Services, Oracle Workspaces, Ultrasearch Crawler, and some of the Search functionality of Oracle Collaboration Suite are not certified.

None

4902653, 4932781, 4930955

Since Verify Filters are not available on Solaris x86_64, some of the Search functionality of Oracle Collaboration Suite are not certified.

None

5212348, 5181385

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 all on one line (where you see <space>, enter a space character):

    ./java  -classpath $ORACLE_HOME/jlib/ldapjclnt10.jar:$ORACLE_HOME/jlib/ojmisc.jar:$ORACLE_HOME/ocal/jlib/ocal_infostore.jar<space>
oracle.calendar.infostore.configuration.InfoStoreConf -t seed -oraclehome $ORACLE_HOME  -schemap<space>
<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.sl # Oracle Calendar app services
plugin02 = ./liblexwebhtml.sl # Oracle Calendar Web Client
plugin03 = ./liblexxml.sl     # Oracle Calendar Web Services
plugin04 = ./liblexsyncml.sl  # 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 your Linux system does not pass the kernel check, and then you correct your kernel settings, clicking Retry checks the old settings, rather than the corrected settings, and the check fails again.

Navigate back and then forth one page in the Oracle Universal Installer, then click Retry. If the kernel settings have been appropriately modified, the check should pass.

3966646

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.

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 3.1.3.14, "Installing or Upgrading using non-Oracle Internet Directory Superuser Accounts"

4536195

Multiple-domain installations of Oracle Discussions against the same mailstore database can lead to unpredictable behavior.

Install different Oracle Discussions domains into different mailstore databases.

4681847

Stand-alone installation of Oracle Calendar on Red Hat Linux 4.0 fails.

Follow the instructions in Section 3.1.3.17, "Installing a Stand-Alone Oracle Calendar Applications Tier on Red Hat Linux 4.0"

4561453

Enabling an existing database for Oracle Collaboration Suite may result in a Configuration assistant "Register Oracle10g Database with OID" failed error.

When installing on an existing 'Collaboration Suite Database' Oracle home, do not select "Enable an existing Oracle10g Database to Collaboration Suite Database". This is supported only on an Oracle home that is Oracle10g Database, not Oracle Collaboration Suite database.

4686427

Installing Oracle Internet Directory (OID) and Oracle Directory Integration and Provisioning (DIP) into two different Oracle homes is not supported.

None.

4673854

When installing Oracle Collaboration Suite in a Single-Cluster Architecture High-Availability Environment, if the Oracle Mobile Collaboration Wireless Instance URLs are set to point to a load balancer virtual server set to port 80, and the port number is not explicitly declared, the Wireless Notification Server will hang during startup in the INIT state.

You must explicitly declare the port number of the load balancer virtual server, even if it is port 80. See Section 3.1.6.4, "Setting the Load Balancer Virtual Server Port for the Wireless Notification Server".

4713614

When using the Applications tier SSL Configuration Tool on an Applications tier host, the DCMCTL UpdateConfig may become unresponsive.

None

4641767

When importing a statistics log file from a 10.1.0.4 ORACLE_HOME to a remote 10.2 database, the Mail Configuration Assistant becomes unresponsive.

  1. Use the following command to identify the process ID that is causing the problem:

    ps -ef |grep imp

  2. Kill the process ID:

    kill -9 process_id

    (Where process_id is the ID of the process being killed.)

    The Mail Configuration Assistant should now complete successfully.

  3. From the 10.1.0.4 Relational Database Management System (RDBMS) Oracle Home, download $ORACLE_HOME/oes/bin/em_stats.dmp to the 10.2 Relational Database Management System.

  4. Run the following command on the 10.2 Relational Database Management System:

    $ORACLE_HOME/bin/imp file=em_stats.dmp fromuser=opt_stats touser=es_stats tables=GMGIT_ES_MAIL_STATS

  5. When prompted for a user name and password, use sys credentials.

4708319

If you have installed Enterprise Manager Agent 10.2 on Microsoft Windows, and then you subsequently install Oracle Voicemail & Fax on the same Applications tier, the Configuration Assistant Tool to Create the PBX and OVF Applications tier targets in Central Console fails.

After the configuration is complete, run the Configuration Assistant Tool from a command window and execute the following commands:

EMAGENT_HOME\bin\emctl config agent addTargetsToRepository
%ORACLE_HOME%\um\scripts\upload_targets.xml true

Where EMAGENT_HOME is where Enterprise Manager 2.0 is installed.

4725825

During the configuration stage of enabling an existing Oracle Database 10.2, the Oracle Web Access client Configuration Assistant fails due to missing libjmisc.so.

Copy libjmisc.so from $ORACLE_HOME/lib in an Oracle Collaboration Suite 10.1.2 infrastructure to the $ORACLE_HOME/lib of the 10.2 database, then retry the Oracle Web Access client Configuration Assistant.

4707642

3.1.5 Globalization Issues in Oracle Collaboration Suite Installation

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

Table 3-3 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 Oracle Content Services is installed in languages other than English, the characters e and s are mapped to the Delete key for the Web interface. Because of this, pressing e or s in some circumstances can cause a selection to be deleted.

See Section 3.1.3.19, "Globalization Shortcut Keys for Oracle Content Services" for the workaround.

4716518

When attempting to install a default Oracle Collaboration Suite database on a host whose domain name includes a dash ("-"), the Database Configuration Assistant does not work.

Run the installer using the following command:

runInstaller OUI_HOSTNAME=machine.domain.com

Where machine and domain are the strings that comprise your domain name and can include dashes.

4567889

3.1.6 Documentation Issues in Oracle Collaboration Suite Installation

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

3.1.6.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

3.1.6.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)

3.1.6.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)

3.1.6.4 Setting the Load Balancer Virtual Server Port for the Wireless Notification Server

In step 5 of "Configure Oracle Collaboration Suite Mobile Collaboration" in Chapter 12 of Oracle Collaboration Suite Installation Guide for Linux, you configure the Oracle Mobile Collaboration Wireless Instance URLs to point to the virtual name of the load balancer used in your Single-Cluster Architecture High-Availability Environment. Ordinarily, if the load balancer is set to port 80, you do not need to specify the port value in Oracle Collaboration Suite. However, due to issue 4713614, you must explicitly declare the port value in step 5, even if it is port 80.

In the Oracle Collaboration Suite Install Guide, Step 5 is:

Modify the Wireless Instance URLs to point to the load balancer's virtual server name (apps_virtual.mycompany.com).

However, Step 5 should read:

Modify the Wireless Instance URLs to point to the load balancer's virtual server name (apps_virtual.mycompany.com:80)

3.1.6.5 Steps for Configuring Oracle Calendar Administration

Steps 1 and 2 in 9.2.8.11 Configure Calendar Administration are inaccurate and should instead be described as follows:

Perform the following steps to enable the Oracle Calendar administrator to work through the Oracle Collaboration Suite Applications middle tier load balancer virtual server:

  1. Add the following lines to the end of the $ORACLE HOME/Apache/Apache/conf/httpd.conf file on each Oracle Applications Oracle home:

    include "<full ORACLE_HOME path>/ocad/config/ocad.conf"

    # include the Oracle configuration file for Calendar Server

  2. Execute the $ORACLE_HOME/dcm/bin/dcmctl updateconfig command so that changes are processed. This will enable Oracle Calendar administrator.

3.2 Oracle Collaboration Suite Upgrade


Notes:

The release note information described in the following sections applies when upgrading from Oracle Collaboration Suite 9.0.x to 10.1.2.

To upgrade from Oracle Collaboration Suite 10.1.1 to 10.1.2, you must patch version 10.1.1 with the Oracle Collaboration Suite 10.1.2 Patch Set. This Patch Set includes a README.html file that contains installation instructions and describes issues specific to the Patch Set. To get the Patch Set, navigate to http://metalink.oracle.com and download patch 4713160.

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

3.2.1 Resolved Issues in Oracle Collaboration Suite Upgrade

Table 3-4 lists resolved issues in Oracle Collaboration Suite upgrade.

Table 3-4 Resolved Issues in Oracle Collaboration Suite Upgrade

Description Resolved In Bug Number

The Upgrade Assistant for Oracle Calendar Web client 9.0.3 did not work.

10.1.2

4477847

In the Oracle Calendar Web client, version 9.0.4 colors were retained after upgrade.

10.1.2

4453255

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

10.1.2

4513034, 4526818, 4540048

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

10.1.2

4477138

Issue requiring steps to Grant Oracle Real-Time Collaboration Users BUSINESSADMIN and BUSINESSMONITOR Roles is now resolved.

10.1.2

4477138

3.2.2 Known Limitations and Workarounds in Oracle Collaboration Suite Upgrade

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

3.2.2.1 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.

3.2.2.2 Mailstore Upgrade can Fail with ORA-29855

While following the instructions in "Enabling Collaboration Suite Schema Creation in the Database Upgrade Assistant" in chapter 5 of Oracle Collaboration Suite Upgrade Guide, ORA-29855 with an Oracle Text error ORA-20000 may occur. If this happens, work around the problem as follows. (4699586)

  1. At the SQL prompt to which ORA-29855 was returned, enter the following commands.

    drop index es_ot_ix_doc;

    drop index es_ot_ix_search;

  2. Enter the following command.

    @oes/install/sql/recreate_text_index.sql

  3. If recreate_text_index.sql printed a message that indicates successful completion of index creation similar to the following, skip to Step 5.

    Creating text index...
PL/SQL procedure successfully completed.

  4. If the error persists, run:

    BEGIN ctx_ddl.drop_preference('es_search_filter'); END;
BEGIN
ctx_ddl.create_preference('es_search_filter', 'MAIL_FILTER');
ctx_ddl.set_attribute('es_search_filter','index_fields','From:To:CC:Subject:Sender:Content-Disposition');
ctx_ddl.set_attribute('es_search_filter','PART_FIELD_STYLE','text');
END;

  5. Enter the following command to execute recreate_text_index again:

    @oes/install/sql/recreate_text_index.sql

3.2.2.3 Creating Realms with Oracle Internet Directory

After upgrading, trying to create realms in Oracle Internet Directory using the Self Service Console results in the following error (4709220):

Cannot Create Identity Management Realm : Invalid Root Oracle Context. [LDAP:
error code 50 - Insufficient Access Rights ]

To avoid this problem, do the following workaround after the Infrastructure upgrade or after all the tiers have been upgraded.

  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 realm parent, such as dc=com | dc=visioncorp.

    3. Select the Subtree Access tab.

  4. Grant access rights to cn=ASPAdmin on the realm parent entry as follows:

    1. Under Entry Level Options click Create.

    2. Select the By Whom tab.

    3. Select A Specific Group.

    4. Enter the following:

      cn=ASPAdmins,cn=groups,cn=visioncorpContext,dc=us,dc=visioncorp,dc=com

    5. Select the Access Rights tab.

    6. Grant Browse, Add and Delete access.

  5. Grant access rights to cn=ASPAdmin on the realm parent attribute as follows:

    1. Under Attribute Level Options click Create.

    2. Select the By Whom tab.

    3. Select A Specific Group.

    4. Enter the following:

      cn=ASPAdmins,cn=groups,cn=visioncorpContext,dc=us,dc=visioncorp,dc=com

    5. Select the Attribute tab.

    6. Make sure EQ and * are entered in the 2 fields.

    7. Select the Access Rights tab.

    8. Grant Read, Search, Write and Compare access rights.

    9. Click Apply.

  6. Expand Entry Management and navigate to cn=visioncorpContext > cn=Groups > cn=ASPAdmins.

  7. In the Properties tab, make sure that cn=orcladmin exists in the uniquemember field.

  8. Click Apply (if necessary).

3.2.2.4 Do Not Use Oracle Application Server Patch Set 10.1.2.1

If you upgrade to Oracle Collaboration Suite 10g Release 1 (10.1.2) from version 9.0.x, do not apply the Oracle Application Server 10.1.2.1 Patch Set.

The only circumstance under which you should apply the Oracle Application Server 10.1.2.1 Patch Set is after patching an Oracle Collaboration Suite 10.1.1 installation with the Oracle Collaboration Suite 10.1.2 Patch Set. As mentioned previously, this upgrade path is not described in this document, but you can find more information in the README.html file included with the 10.1.2 patch set. The 10.1.2 patch set is available from http://metalink.oracle.com (patch 4713160).

3.2.2.5 Ultrasearch Configuration Assistant May Fail

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

Failed to create service entries for existing 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 following catalogs were created in Oracle Internet Directory using an Oracle Collaboration Suite tool or a manual workaround:

  • targetdn

  • orclownerguid

  • pager

  • personalmobile

  • personalpager

  • middlename

  • orclSuiteType

  • orclServiceType

  • orclServiceSubType

  • orclServiceMember

  • orclstatus

In this case, during the upgrade, the command to create these catalogs fails, and subsequent catalogs for other components are also not created.

To check if a catalog exists, log in to the Metadata Repository Database as the ODS user and then perform the following command:

desc ct_catalog_name;

In the preceding command, catalog_name should be replaced by the name of the catalog you need to check.

For example, the command to check whether the targetdn catalog exists will be:

desc ct_targetdn;

If the message Òct_catalog_name does not existÓ is displayed, then you can proceed with the upgrade normally, without the need of any additional steps. However, if this message is not displayed, then you must perform the following workaround.

Workaround

You must perform the following steps:

  1. Before upgrading Oracle Internet Directory, remove the catalogs using catalog.sh.

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

    In the preceding command, replace catalog_name with the name of the catalog you need to remove.

    For example, to remove the targetdn catalog:

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

    In the preceding comamnd, connect_string is the database connect string for the Infrastructure database, such as asdb.


    Note:

    After this step you must upgrade Oracle Internet Directory.

3.2.3 Known Issues in Oracle Collaboration Suite Upgrade

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

Table 3-5 Known Issues in Oracle Collaboration Suite Upgrade

Description Action Bug Number

After upgrade, the following issues may appear:

  • The Ultrasearch admin URL on the Applications tier home page is unavailable.

  • When the Applications tier is secured using the Applications tier SSL configuration tool, the Ultrasearch admin URL on the Applications tier home page still uses http instead of https.

Download and apply patch 4901434 from http://metalink.oracle.com.

4901434

Upgrading a RAC database on RAW devices

The Oracle Real-Time Collaboration Configuration Assistant always copies the RAW configuration file from its original location to $ORACLE_HOME/imeeting/ on the node the installer is launched from. It also uses the Real Application Clusters connect string to contact one of the Real Application Clusters instances at random. If $ORACLE_HOME/imeeting/RAW_CONFIG_FILE does not exist on that instance, the read operation fails and the Oracle Real-Time Collaboration Configuration Assistant also fails.

Manually copy the RAW configuration file to $ORACLE_HOME/imeeting/ on every Real Application Clusters instance.

4536166

During a standalone upgrade from 9.0.x to 10.1.2, the file $ORACLE_HOME/ocas/upgrade/ocasua.sh does not get instantiated from the corresponding SBS file.

Manually instantiate the file as follows:

  • Back up $ORACLE_HOME/upgrade/ocasua.sh to $ORACLE_HOME/upgrade/ocasua.sh.bak.

  • Copy the newly installed $ORACLE_HOME/upgrade/ocasua.sh.sbs to $ORACLE_HOME/upgrade/ocasua.sh.

  • Use a text editor to replace every occurrence of %ORACLE_HOME% with the actual path of your oracle home.

  • Use a text editor to replace every occurrence of %UAJAVAHOME% with the actual path of your oracle home appended with /jdk.

4694839

3.2.4 Globalization Issues in Oracle Collaboration Suite Upgrade

There are no known globalization issues for Oracle Collaboration Suite upgrade.

3.2.5 Documentation Issues in Oracle Collaboration Suite Upgrade

There are no known documentation issues for Oracle Collaboration Suite upgrade.

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