| Oracle® Collaboration Suite Release Notes 10g Release 1 (10.1.1) for Windows Part Number B15506-01 |
|
|
View PDF |
| Oracle® Collaboration Suite Release Notes 10g Release 1 (10.1.1) for Windows Part Number B15506-01 |
|
|
View PDF |
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 version of this document was updated on August 1, 2005 at 5:38 pm Eastern Daylight Time (UTC/GMT -4 hours). For the latest version of this document, navigate to:The following topics describe release note information associated with Oracle Collaboration Suite installation.
Section 1.1.1, "New in Oracle Collaboration Suite Installation"
Section 1.1.2, "Known Limitations and Workarounds in Oracle Collaboration Suite Installation"
Section 1.1.3, "Known Issues in Oracle Collaboration Suite Installation"
Section 1.1.4, "Documentation Issues 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.
The following sections describe known limitations and workarounds for Oracle Collaboration Suite installation and configuration:
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 when those versions are made available.
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:
Manually kill idms processes.
Launch Oracle Real-Time Collaboration Control from $ORACLE_HOME/imeeting/bin.
From Oracle Real-Time Collaboration Control, run getstate -v to fetch the id number of the Instant Messaging router (imrtr).
From Oracle Real-Time Collaboration Control, run stop -cid id_number_for_imrtr.
From Oracle Real-Time Collaboration Control, run start -cid id_number_for_imrtr.
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:
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:
Section 1.1.2.4.3, "Checking the NLS_LANG Environment Variable"
Section 1.1.2.4.4, "Setting the NLS_LANG Environment Variable"
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
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
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.
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"
The following table lists suite-level known issues in Oracle Collaboration Suite installation and configuration.
Table 1-1 Known Issues in Oracle Collaboration Suite Installation
| Description | Action | Bug Number |
|---|---|---|
|
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 |
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 [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:
|
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 |
|
The Oracle Discussions Configuration Assistant sometimes appears to have run successfully, when in fact it has failed. |
None |
4511808 |
|
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 |
|
Linux only: If your 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. You should also apply this patch if you encounter any of the issues listed in Section 1.2.1.1 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 |
|
On deinstallation, Oracle Internet Directory entries are not automatically deleted. |
Manually delete the entry as follows:
The Oracle Collaboration Suite Console Application identity for this Applications tier will be deleted from Oracle Internet Directory. |
4486439 |
The following table lists globalization issues in Oracle Collaboration Suite installation and configuration.
The following section describes documentation issues for Oracle Collaboration Suite installation.
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
The following topics describe release note information associated with upgrading Oracle Collaboration Suite.
Section 1.2.1, "Known Limitations and Workarounds in Oracle Collaboration Suite Upgrade"
Section 1.2.2, "Known Issues in Oracle Collaboration Suite Upgrade"
This section describes known limitations and workarounds for Oracle Collaboration Suite 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.
Before configuring Oracle Content Services, configure Oracle Workflow by performing the following steps:
Log in to the Oracle Collaboration Suite Database as a user with appropriate privileges and enter the following command:
drop user owf_mgr cascade;
From the Oracle Collaboration Suite Database Oracle home, run the following script:
$ORACLE_HOME/wf/install/wfinstall.csh
The Oracle Workflow Configuration Assistant starts.
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 Enter LDAP Parameters, Enter Mailer Parameters, or Change Tablespace.
Click Submit.
Proceed with configuring Oracle Content Services using the Oracle Collaboration Suite Control Console.
Make sure the passwords entered in the Specify Database Schema Passwords dialog box during the Infostore upgrade are correct. They are are not being validated and can cause the upgrade to fail if incorrect. (4510605)
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).
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:
In Oracle Internet Directory, 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.
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 user name
PASSWORD is Oracle Ultra Search password
INSTANCE_NAME is the Oracle Ultra Search instance name
Delete the cached version of the file in $ORACLE_HOME/j2ee/OC4J_OCSClient/application-deployments/default/UltraSearch/oc4j-ra.xml.
Restart the OC4J_OCSClient instance.
The following table lists known issues in Oracle Collaboration Suite upgrade.
Table 1-3 Known Issues in Oracle Collaboration Suite Upgrade
| Description | Action | Bug Number |
|---|---|---|
|
When upgrading standalone Oracle Calendar application system installations, the upgrade assistant does not accept the |
Do not use the /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 1.2.1.1. |
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 |
On the system running the upgraded Applications tier, perform the following steps where $ORACLE_HOME is the upgraded Applications tier Oracle home:
|
4513034 |
|
Passwords entered in the Specify Database Schema Passwords dialog box are 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 1.2.1.3, "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 To verifythat the crawling is complete:
|
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 1.2.1.2 |
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 1.2.1.5. |
4519770 |
