| Oracle® Beehive Release Notes Release 2 (2.0) for Linux, Windows, and Solaris Operating System (SPARC 64-Bit) Part Number E16640-11 |
|
|
PDF · Mobi · ePub |
| Oracle® Beehive Release Notes Release 2 (2.0) for Linux, Windows, and Solaris Operating System (SPARC 64-Bit) Part Number E16640-11 |
|
|
PDF · Mobi · ePub |
This module contains the following types of information related to Oracle Beehive installation and configuration:
This section contains general information about the installation and configuration of Oracle Beehive. It contains the following topic:
Additional Patch Required When Installing Oracle Beehive on Oracle Database 11.2.0.1
Apply Patch to Oracle Database 11.1.0.7.x on Certain Locales
Oracle Beehive 2.0.1.2.0 Available as Full Install/Upgrade or Cumulative Patch Set
Configuring Oracle Beehive Webmail in Same Oracle_Home as Oracle Beehive
Additional Patch Required When Installing on Oracle Database 11.2
Oracle Beehive 2.0.1.8.0 Available as Upgrade or Cumulative Patch Set
In Chapter 2, "Oracle Beehive Database Requirements" of the Oracle Beehive Installation Guide, the section "Patches" lists patches required for Oracle Database 11g Release 2 (11.2.0.1). In addition to those listed, you should also apply the following patch:
9328390 - ET11.2SQLEXEC: ORA-600 [QERIXGETKEY:OPTDESC] FROM QUERY
Bug 9948554. Due to database bug 8481520, after installing Oracle Beehive 2.0.1.3.0 or 2.0.1.4.0 patch set, customers using Oracle DB version 11.1.0.7.x who are installing on French, German, Italian, Spanish, or Portuguese (Brazilian) locales should install an Oracle Database patch.
On Linux x86, x86-64, and Oracle Solaris on SPARC (64-bit), download and install the patch for Bug 8481520.
On Windows or other operating systems, contact Oracle Support for the necessary patch.
Oracle Beehive 2.0.1.2.0 is available as either a full install/upgrade, using the Oracle Universal Installer; or, as the 2.0.1.2.0 Cumulative Patch Set, which applies updates to any pre-existing 2.0.1.0.0 or 2.0.1.1.0 installation.
For information about installing the 2.0.1.2.0 Cumulative Patch Set, see the readme at the following URL:
http://www.oracle.com/technology/products/beehive/patchdoc/beehive_20120_readme.htm
For the full install/upgrade, you can use the Oracle Beehive 2.0 Installation Guide for your platform, and the installer integrated help.
Table 4-1, "Oracle Beehive Upgrade Options for 2.0.1.2.0" shows the upgrade and patch options that are available.
Table 4-1 Oracle Beehive Upgrade Options for 2.0.1.2.0
| Your current Oracle Beehive deployed version | Your upgrade path option(s) |
|---|---|
|
1.5.1.0.0, 1.5.1.2.0, 1.5.1.3.0, 1.5.1.4.0 |
Either:
|
|
1.5.1.5.0, 1.5.1.5.1, or 1.5.1.5.2 |
Either:
|
|
2.0.1.0.0, 2.0.1.1.0 |
You must upgrade using 2.0.1.2.0 Cumulative Patch Set only. You cannot use the 2.0.1.2.0 OUI installer. |
Oracle Beehive Webmail will be installed and configured in the same Oracle_Home as Oracle Beehive if you install Oracle Beehive on a computer with at least 3 gigabytes (GBs) of memory and you select the Server + Client template during the installation process.
Note:
The requirement described here applies to 64-bit systems running supported Red Hat Linux and Oracle Linux operating systems only.If you plan to deploy Oracle Beehive for Linux on a 64-bit system running a supported Red Hat Linux or Oracle Linux operating system, ensure that the following packages are installed on your system beforehand:
gdbm-1.8.0-26.2.1-i386.rpm (32-bit)
glibc-devel-2.3.4-2.19.i686.rpm (32-bit)
glib-devel-1.2.10-15-i386.rpm (32-bit)
glib-1.2.10-15-i386.rpm (32-bit)
These packages should be installed in addition to the packages listed in "Requirements for 64-Bit Systems" section in the Oracle Beehive Installation Guide for Linux.
In Chapter 2, "Oracle Beehive Database Requirements" of the Oracle Beehive Installation Guide, the section "Patches" lists patches required for Oracle Database 11g Release 1 (11.1.0.7.0) and Release 1 (11.1.0.7.2). When upgrading to Oracle Beehive Release 2 (2.0.1.2.0 or later), in addition to those listed, you should also apply the following patch:
8440319 LINGUISTIC APIS FOR TACIT
In Chapter 2, "Oracle Beehive Database Requirements" of the Oracle Beehive Installation Guide, the section "Patches" lists patches required for Oracle Database 11g Release 2 (11.2.0.1). In addition to those listed, you should also apply the following patch:
8654177 - 80: PLACEHOLDER FOR BUGFIXES TO BACKPORT 8440319 THAT ARE NOT IN 11.2
To avoid issues, especially when patching or upgrading Oracle Beehive, Oracle recommends single-line database connection strings. The database connect string should not contain any new line characters (for example, \n, \r, or \n\r).
Oracle Beehive 2.0.1.8.0 is available as upgrade, using the Oracle Universal Installer; or, as the 2.0.1.8.0 Cumulative Patch Set, which applies updates to pre-existing version installation as shown in the Table 4-2, "Oracle Beehive Upgrade Options for 2.0.1.8.0".
For information about installing the 2.0.1.8.0 Cumulative Patch Set, see the readme at the following URL:
http://www.oracle.com/pls/bee2/homepage
For the full install/upgrade, you can use the Oracle Beehive 2.0 Installation Guide for your platform, and the installer integrated help.
The following table shows the possible upgrade and patch options that are available:
Table 4-2 Oracle Beehive Upgrade Options for 2.0.1.8.0
| Your current Oracle Beehive deployed version | Upgrade path option(s) |
|---|---|
|
1.5.1.0.0, 1.5.1.2.0, 1.5.1.3.0, 1.5.1.4.0 |
|
|
1.5.1.5.0, 1.5.1.5.1, or 1.5.1.5.2 |
|
|
2.0.1.0.0, 2.0.1.1.0, 2.0.1.2.0, 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, 2.0.1.6.0, and 2.0.1.7.0 |
Apply 2.0.1.8.0 Cumulative Patch Set. |
This section contains information about known limitations and workarounds related to the installation and configuration of Oracle Beehive. It contains the following topics:
Additional Step when Configuring Oracle Beekeeper for LDAP-Based Authentication
Multiple Cloned Instances From Same Clone Tree Not Recommended
Spaces in Installation Package Directory Path Prevent Installer from Launching
Installing Oracle Beehive on Sun Solaris May Fail During Core Configuration
File May Cause Installation of Oracle Beehive on Linux and UNIX-based Operating Systems to Fail
CNS Service May Fail to Start During Installation on Coexistence Connector for Exchange
Post-Install Step to Upgrade Mobile Device Management Service Not Needed
Bug 9815576. In Chapter 31, "Oracle Beekeeper Post-Installation Procedures" (Chapter 33 in the Windows version) of the Oracle Beehive Installation Guide, Step 7 of "Configuring Oracle Beekeeper for LDAP-Based Authentication" indicates that you should copy the obfuscated password to the <Oracle Beekeeper home>/j2ee/home/application-deployments/javasso/jps-config.xml file.
You must also copy the obfuscated password to the <Oracle Beekeeper home>/j2ee/home/application-deployments/beekeeper/jps-config.xml file.
A clone tree consists of an Oracle Beehive instance (the source instance), instances cloned from the source instance, and instances cloned from clones of the source instance. Oracle does not recommend deploying more than one Oracle Beehive instance from the same clone tree. However, if you think this might be the best option for you, contact your Oracle Support representative.
Note:
This known limitation affects Oracle Beehive Release 1 (1.3.2.0.0) and later for the Microsoft Windows (32-bit) only.If your installation package resides in a directory path that contains spaces, you will not be able to launch the installation by double-clicking the setup.exe icon within the Disk1 directory. Either run setup.exe from a command shell or move your installation package to a path that does not contain spaces.
Bug 7326046. Attempts to install Oracle Beehive Webmail on an Application Tier computer configured for TLS with test certificates may fail. Administrators can avoid this issue by ensuring that the specified Oracle Wallet contains real certificates. For more information, contact Oracle Support.
Note:
This known limitation affects Oracle Beehive Release 1 (1.3.2.0.0) and later for Solaris Operating System (SPARC 64-bit) only.Bug 7332530. Installing Oracle Beehive on the Sun Solaris operating system may fail during the Core Configuration CA step. To avoid this issue, Oracle recommends installing Sun Solaris patch 127127-11.
Bug 7489313. If you use Oracle Enterprise Manager Grid Control to install Oracle Beehive, the automatic memory prerequisite check may return an incorrect value for available physical memory. This is due to an issue with Oracle Universal Installer that rounds down the actual value.
In some cases, the incorrect value may appear to be too low to successfully install certain components, such as Oracle Beehive Webmail. Oracle Enterprise Manager Grid Control may even reflect this incorrect assessment in its log files. However, if there is enough actual physical memory available, you will receive a message that states the memory check passed (despite the log file entry to the contrary) and all components will install correctly.
Bug 8283818. On large deployments, integrating Oracle Single Sign-On (OSSO) with Oracle Beehive may cause a significant increase in the memory allocation for Beehive JVM BEECORE, which may result in a degradation of system performance.
Contact your Oracle support representative for details.
Note:
This issue applies to deployments on supported Linux and UNIX-based operating systems only.Installing Oracle Beehive on a computer running a Linux or UNIX-based operating system may fail if the tnsnames.ora file already exists in any of the following directories:
/etc
/var/opt/oracle
To avoid this issue, either delete or rename tnsnames.ora before installing Oracle Beehive. If you choose to rename the file, you can change it back to its original name after you install and configure Oracle Beehive.
Note:
This issue applies to Oracle Beehive Coexistence Connector deployments which have been upgraded from 1.5.1.5.x to 2.0.1.2.0 only.Bug 9677425. During an upgrade to Oracle Beehive 2.0.1.2.0 using Oracle Universal Installer (OUI), If the configuration assistant fails in starting the CNS service, run the following command:
$ORACLE_HOME\beehive\collabcoex_connector\coexctl.exe install_eventsink --install_directory $ORACLE_HOME\beehive\collabcoex_connector --admin_account <coexAdminUser> --admin_password <coexAdminPwd>
Optionally, you can omit the --admin_password option, and enter the password when prompted.
After the command runs, click Retry in the OUI upgrade wizard.
In Chapter 12, "Upgrading Oracle Beehive Overview" of the Oracle Beehive Installation Guide 2.0 (Chapter 13 in the Windows version), the section "Upgrading Mobile Device Management Service After Oracle Beehive Upgrade" is no longer needed. You can safely skip this step when upgrading Oracle Beehive.
|
 Copyright © 2008, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
