| Oracle® Beehive Release Notes Release 1 (1.5) Part Number E14829-08 |
|
|
View PDF |
| Oracle® Beehive Release Notes Release 1 (1.5) Part Number E14829-08 |
|
|
View PDF |
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:
Oracle Beehive Zimbra 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 operating systems only.If you plan to deploy Oracle Beehive for Linux on a 64-bit system running a supported Red Hat 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.
This section contains information about known limitations and workarounds related to the installation and configuration of Oracle Beehive. It contains the following topics:
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
"Missing Streams" Message May Appear in Logminer Log File During Oracle Beehive Installation
Deploying Oracle Beehive With Non-ASCII Data Fields Requires UTF-8 Encoded Locales
Oracle Beehive Install Wizard Does Not Restore Previously Selected Template Choice
Upgrade to Oracle Beehive Release 1 (1.5) Will Fail if tnsnames.ora Does Not Exist
Oracle Beehive Installation Fails if Oracle Home and Installation Media on Different Partitions
File May Cause Installation of Oracle Beehive on Linux and UNIX-based Operating Systems to Fail
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. Please 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 Integration for Zimbra 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, please 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.
Note:
This issue only affects deployments that use Oracle Enterprise Manager Grid Control 10.2.0.4 to install and configure Oracle Beehive.Bug 7362094. Attempts to install Oracle Beehive with Oracle Enterprise Manager Grid Control 10.2.0.4 using non-ASCII characters in either the enterprise or organization name field will fail. To avoid this issue, do not use non-ASCII characters in either of these fields.
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 Zimbra. 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 6317006. During the Oracle Beehive installation process, Logminer might log one or more messages in its log file indicating "missing streams". These messages are the result of Logminer attempting to mine a database table that is unrelated to Oracle Beehive. Therefore, please ignore these messages.
Bug 8309265. Specifying a nonexistent directory path for the Software Library Location during the Oracle Beehive Provisioning Application installation will result in an error. To avoid this issue, at the interview screen for the Software Library Location in the Provisioning Application installation, ensure that you specify an absolute, non-empty directory path.
For example:
/app/oracle/<software_lib_location> (UNIX)
or
c:\app\oracle\<software_lib_location> (Windows)
where <software_lib_location> is the existing folder for the Software Library Location.
Note:
This limitation applies to deployments on supported UNIX and Linux operating systems only.Bugs 7362094 and 8370724. If you plan to deploy Oracle Beehive using non-ASCII data for your enterprise, organization, or site, the computers that you intend to host the Oracle Beehive server must use a locale with UTF-8 encoding, such as fr_FR.utf8 or zh_TW.utf8.
You can ensure this by setting the LC_ALL and LANG environment variables appropriately on the console where the agent for Oracle Enterprise Manager Grid Control starts.
Bug 7629704. If you exit the Oracle Beehive Install Wizard prior to completing the installation process and then reenter the wizard, you will be asked to complete any missing interview questions. For the Template section, ensure that you choose the same template that you chose during the original installation attempt. The Install Wizard will not restore the previously selected Template choice for you.
Note:
This issue is resolved in Oracle Beehive Release 1 (1.5.1.1) and later.Bug 8374920. Deployments with large numbers of calendar assignments (>10,000) may experience higher database loads after upgrading to Oracle Beehive Release 1 (1.5). This issue is caused by a background task that can consume an increasing amount of database processing resources if large numbers of assignments exist. In addition to higher database loads, database session timeouts may also occur.
For instructions on how to prevent and resolve this issue, please contact Oracle Support.
Note:
This issue only applies to deployments that originally installed Oracle Beehive Release 1 (1.2) or Release 1 (1.3). If your organization first deployed Oracle Beehive Release 1 (1.4) or later, the issue described here does not apply.Bug 8407373. If your organization installed Oracle Beehive Release 1 (1.2) or Release 1 (1.3) and subsequently cloned one or more application tiers or sites, the upgrade to Oracle Beehive Release 1 (1.5) may fail. To avoid this issue, please refer to the steps provided in the “Before Upgrading” section of the Oracle Beehive Installation Guide for your operating system.
Note:
This issue only applies to deployments that applied an Oracle Application Server Critical Patch Update (CPU) patch to one or more Oracle Beehive Release 1 (1.4.3) application tiers.The upgrade to Oracle Beehive Release 1 (1.5) may fail if your organization applied an Oracle Application Server Critical Patch Update (CPU) patch to any of your Oracle Beehive Release 1 (1.4.3) application tiers. To avoid this issue, follow the steps described in OracleMetaLink Note 735631.1, "Symbol Referencing Error on nzospRandNum When AS Patchset Applies Patch 4601861 (CPU Patch Previously Applied)." Oracle MetaLink Note 735631.1 describes how to roll back previously applied CPU patches and apply the latest CPU patch for the new patchset version.
Bug 8274411. The installation for Oracle Beehive Release 1 (1.5) may fail if the name of your global database contains a hyphen (-) or begins with a digit. To avoid this issue, ensure that the global database name used by your Oracle Beehive deployment does not contain a hyphen or begin with a digit.
Note:
This issue only applies to deployments that originally installed Oracle Beehive Release 1 (1.2) or Release 1 (1.3). If your organization first deployed Oracle Beehive Release 1 (1.4) or later, the issue described here does not apply.Bug 8439537. If your organization originally installed Oracle Beehive Release 1 (1.2) or Release 1 (1.3), the tnsnames.ora file may not exist in your deployment. If this is the case, the upgrade to Oracle Beehive Release 1 (1.5) will fail. To avoid this issue, please refer to the steps provided in the “Before Upgrading” section of the Oracle Beehive Installation Guide for your operating system.
Note:
This issue only affects deployments that upgrade to Oracle Beehive Release 1 (1.5) for Linux on the following supported operating systems:SuSE Linux Enterprise 9.0 with Service Pack 2 and later
SuSE Linux Enterprise 10.0
Bug 8463832. The Upgrade Assistant for Oracle Beehive Release 1 (1.5) for Linux does not change the max heap memory size setting (as it should) during the upgrade process on the SuSE Linux Enterprise 9.0 and SuSE Linux Enterprise 10.0 operating systems only. As a result, the upgrade to Oracle Beehive Release 1 (1.5) fails when deployed on these operating systems.
To resolve this issue, complete the following steps:
After the failure, access the wsmadmin.sh file in the following location:
$OH/owsm/bin/
In wsmadmin.sh, search for all instances of the value 2048 and replace them with the value 1024.
Save wsmadmin.sh.
Retry the Upgrade Assistant. The upgrade should complete successfully.
Bug 8283818. Integrating Oracle Single Sign-On (OSSO) with Oracle Beehive will cause a significant increase in the memory allocation for Beehive JVM BEECORE, which may result in a degradation of system performance.
Bug 8501498. Attempts to install Oracle Beehive Release 1 (1.5) for Microsoft Windows on deployments where your Oracle Home and the Oracle Beehive installation media reside on different partitions will fail during the Beehive Schema Configuration Assistant.
If this occurs, complete the following steps to resolve this issue:
In the Oracle Beehive Install Wizard, click Cancel.
Note:
Skip this step if you chose to install Oracle Beehive using the silent install option.Execute the following command:
OH\beehive\oobwiz\configWizard.bat
This launches the Beehive Schema Configuration Assistant and enables you to continue the installation.
Bug 8791914. Upgrading from Oracle Beehive Release 1 (1.4.3) to Oracle Beehive Release (1.5) causes the account for the ORAESB schema to become locked if all of the following are conditions are true:
Your deployment uses Oracle Database 11g Release 1 (11.1.0.7) Enterprise Edition or later.
The password for your ORAESB schema account contains uppercase characters.
The Oracle Database parameter sec_case_sensitive_logon is set to true (in other words, alter system set sec_case_sensitive_logon=true;)
If all of these conditions exist, do at least one of the following before you upgrade to Oracle Beehive Release 1 (1.5):
Change the password for your ORAESB schema account so that it does not contain any uppercase characters.
Set the Oracle Database parameter sec_case_sensitive_logon to false, as follows:
alter system set sec_case_sensitive_logon=false;
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 prior to 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.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
