Skip Headers
Oracle® Beehive 2.0.1.7.0 Cumulative Patch Set Readme
For Oracle Beehive Release 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, and 2.0.1.6.0) (All Platforms)
 

 

Oracle® Beehive

2.0.1.7.0 Cumulative Patch Set Readme

For Oracle Beehive Release 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, and 2.0.1.6.0) (All Platforms)

 

August 2012

Readme last updated on August 3, 2012

This Readme accompanies 2.0.1.7.0 Cumulative Patch Set for Oracle Beehive Release 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, and 2.0.1.6.0).

This option installs 2.0.1.7.0 Cumulative Patch Set, for installations of Oracle Beehive Release 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, and 2.0.1.6.0) only. Before applying this patch, you must upgrade your Oracle Beehive deployment to Release 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, or 2.0.1.6.0). Do not attempt to install this patch set on earlier versions of Oracle Beehive.

Table 1, "Oracle Beehive Upgrade Options for 2.0.1.7.0" shows the upgrade and patch options that are available.

Once you have completed an upgrade according to one of these paths, you can then apply this patch set.

Table 1 Oracle Beehive Upgrade Options for 2.0.1.7.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

Patch to 1.5.1.5.0, then use 2.0.1.2.0 OUI installer, then apply 2.0.1.7.0 Cumulative Patch Set

1.5.1.5.0, 1.5.1.5.1, or 1.5.1.5.2

Use 2.0.1.2.0 OUI installer, then apply 2.0.1.7.0 Cumulative Patch Set

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 and 2.0.1.6.0

Apply 2.0.1.7.0 Cumulative Patch Set



Note:

You can determine your version number by running the beectl version command from any Oracle Beehive Oracle home.

This Readme contains the following topics:

Introduction

This Readme includes information on installation, important notes, and known workarounds for the Oracle Beehive 2.0.1.7.0 Cumulative Patch Set for Oracle Beehive Release 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, and 2.0.1.6.0).

Oracle recommends that you read and understand the information in this document before beginning the installation.

What's New in this Release

Some of the new features included in this release are:

  • Oracle Beehive Extensions for Outlook

    • Auto-repair OBEO COM add-in after it is disabled by Outlook

    • Ability to show multiple resource conflicts for recurring meetings

    • Ability to synchronize working hours from Oracle Beehive Extensions for Outlook and Oracle Beehive Central

    • Auto-terminate Outlook process when it is stuck and cannot exit by itself

  • Oracle Beehive Team Collaboration

    • Link provided to the Oracle Beehive Webmail Calendar in Oracle Beehive Webmail from the Oracle Beehive Team Collaboration UI

    • Link provided to the Oracle Beehive Team Workspace Inbox in Oracle Beehive Webmail from the Oracle Beehive Team Collaboration UI

  • Oracle Beehive Webmail

    • Link provided in the UI to Oracle Beehive Webmail Help and Release Notes

  • Oracle Beehive Workspaces

    • Enhanced export_workspace command

    • Enhanced import_workspace command

    • Workspace support added to beectl export_email_data and beectl import_email_data commands

  • Supported Software Versions

    • Standards based clients

      • Support for MacOS X 10.8 (Calendar 5, Mail 6, Finder, Messages 6)

      • Support for Thunderbird 10.0 ESR with Lightning 1.2

    • Mobile access

      • Support for Nokia Symbian 3

    • Browser support (does not apply to Beekeeper)

      • Firefox 10 ESR

    • Update of the Beehive Timezone package

    • Support for Sun Directory Server ODSEE 11gr1

Review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at:

http://support.oracle.com


Note:

You must register online before using My Oracle Support. After logging in, click Certifications from the menu options. On the Certifications page, use the Certification Search options to search by Product, Release, and Platform. You can also search using the Quick Link options such as Classic Certify & Product Roadmap, Product Availability, and Lifetime Support.

For detailed information on the new features, refer to the Oracle Beehive Release Notes Release 2 (2.0) at the following location:

http://www.oracle.com/pls/bee2/homepage

Important Notes

Please review the following important notes before installing this patch:

Rollback Not Supported

Rollback of this patch is not supported. Before applying this patch, take a backup of both Beehive Database and the Beehive Oracle home.

Set Environment Variable

Set ORACLE_HOME environment variable to your Beehive Oracle home. For example, setenv ORACLE_HOME /app/oracle/products/beehive

Ensure that the Database instance and TNS Listener are up and running.

Ensure Beehive processes are gracefully started and all services are running before shutting down.

Must Install Oracle Beekeeper Prior to Applying Patch

Beekeeper cannot be used without applying the 2.0.1.7.0 Cumulative Patch Set.

BEEKEEPER home can be patched after at least one midtier has been patched in a multi-midtier environment (OR) after all midtiers are patched.

One-off Patch for Database Defect 8440319

Apply the one-off patch for database bug 8440319 (only for 11.1.0.7.0) if not yet applied in Database Oracle home before applying this patch set. Check the README.txt in that patch after unzipping for applying the patch. Make sure post-patch steps are executed as documented in the README.txt. Failure to do that will result in failure when applying this Oracle Beehive patch set.

When Applying the Patch on 1.5.1.x to 2.0.1.0 Environment

If you are applying the patch set in an 1.5.1.x --> 2.0.1.0 upgraded environment in a Beekeeper home, perform the following mentioned workaround before applying the patch set (This is only in Beekeeper upgraded home).

% cd $ORACLE_HOME/.patch_storage% unzip<patch_extract_location>/13361024/Beehive_20170/custom/scripts/beepatch/9041410_workaround.zip

When Applying the Patch on 2.0.1.0.0, 2.0.1.1.0 or 2.0.1.2.0 Environment

If applying on 2.0.1.0.0, 2.0.1.1.0 or 2.0.1.2.0 installation, shutdown all the processes in all Beehive midtiers including BEEKEEPER and DMZ homes before applying the patch set.

When Applying the Patch on 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0 Environment

If applying on 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0 or 2.0.1.6.0 installation, these are ZDU (Zero Downtime Upgrade) and you need not shutdown all midtiers. Shutdown the processes only in the midtier where the patch set is getting applied.

Schema Cloning will be done when applied on top of 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0.

ZDU to 2.0.1.7 on 11.2 must include workaround to Database defect 9345099

When upgrading to 2.0.1.7 on database 11.2, follow the steps below to workaround the database bug 9345099.

  1. Before attempting a ZDU, log in to your Oracle Beehive database as SYS using SQL*Plus, and enter the following command:

    ALTER SYSTEM SET EVENT = '31151 trace name context forever, level 0x100' 
    scope=spfile SID='*';
    
  2. For each database instance, set the following event:

    ALTER SYSTEM SET EVENTS '31151 trace name context forever, level 0x100';
    
  3. Do not disable the event after the upgrade is done.


Note:

Add the above mentioned event to the list of existing events, ensuring not to overwrite any existing events that you may have set.


Note:

Ensure that all the steps for ZDU are strictly followed.

Review Oracle Beehive Release Notes

Before applying this (or any) patch on Oracle Beehive, always review the latest Oracle Beehive Release Notes for complete information about known issues, workarounds, and new features in Oracle Beehive. You can find PDF and HTML versions of the Release Notes on the Oracle Technology Network Web site, at the following URL:

http://www.oracle.com/pls/bee2/homepage

Ensure Sufficient Hard Drive Space Before Patching

Before applying this (or any) patch on Oracle Beehive, ensure there is sufficient hard drive space on the Oracle Beehive server. Oracle recommends at least 10 GB of free space.

Search Service Refactoring Requires Additional Configuration

If you are installing this patch on 2.0.1.2.0 or earlier, the patch includes a refactoring of the Oracle Beehive Search Service (which was added in 2.0.1.2.1). This is a substantial change which may require additional post-configuration steps:

  • The existing search index is erased during patching. As a result, after the upgrade any search operation on existing data will return no results. You can perform post-installation steps to build a new search index of existing artifacts, using a new beectl command, beectl add_search_recovery_scope.

  • If you are using Oracle Secure Enterprise Search (SES) with Oracle Beehive, you must take additional steps to configure SES integration.

  • After the upgrade, the search service is enabled, new objects will be indexed, and default values for partitioning, jobs, and search service parameters are set. Depending on your deployment, you may need to make further configuration changes to tune the search service.

For a brief summary of post-installation steps, see Search Service Post-Installation Configuration. For a detailed explanation of the new search service and its configuration, see MetaLink note 1135054.1.

Configure Data Directories

Depending on whether your Oracle Beehive deployment uses Oracle RAC nodes or not, configure data directories for data pump jobs as per the instructions at:

http://download.oracle.com/docs/cd/E16671_01/bh.200/e16641/upgrade_overview.htm#CJAHGGEC

Installation Requirements

You must conform to each of the following requirements and perform all pre-installation tasks before installing the patch:


Caution:

Failure to carefully read and understand these requirements may cause Oracle Beehive to malfunction, including interruption of service, loss of data, or both.

Install on Oracle Beehive Release 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, 2.0.1.5, and 2.0.1.6) Only

Oracle Beehive 2.0.1.7.0 Cumulative Patch Set can only be installed on Oracle Beehive Release 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, 2.0.1.5, and 2.0.1.6). If you have an earlier version of Oracle Beehive, you must first upgrade to Oracle Beehive Release 2, before applying this patch.

Backup your Oracle Beehive Deployment

Before installing 2.0.1.7.0 Cumulative Patch Set, Oracle strongly recommends that you perform a backup of your database and the Oracle Beehive Oracle home.

Install on All Oracle Beehive Application Tiers

In a multi-midtier environment, you must install this patch in every Oracle Beehive Oracle home, including Application tiers, Oracle Beehive DMZ Oracle Homes, Oracle Beehive Coexistence Connector Oracle Homes, and Oracle Beekeeper Oracle Homes.

Patch has to be applied in the midtiers one by one. All processes in that midtier will be started at the end of patch set.

Except When Patching 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0, Shut Down Oracle Beehive

Unless you are patching an Oracle Beehive 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0 deployment, before installing this patch set, shut down all processes on all Oracle Beehive Application tiers, including Oracle Beekeeper, Oracle Beehive Coexistence Connector, and Oracle Beehive DMZ Oracle homes. Make sure that all Oracle Beehive processes were started normally prior to shutting them down.

If you are patching an Oracle Beehive 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0 deployment, you may perform a Zero Downtime Upgrade (ZDU) patch. In this case, you can leave your Oracle Beehive Application tiers up and running, only shutting down one Application tier server at a time when you patch that server. The ZDU method allows you to avoid downtime of your Oracle Beehive deployment.

Each of your Oracle Beehive servers will be started automatically as you apply the patch set to them.

Disable Fast Validation in the Database

You must disable fast validation in the database before installing Oracle Beehive 2.0.1.7.0 Cumulative Patch Set.

Log in to your Oracle Beehive database as SYS using SQL*Plus, and enter the following command:

ALTER SYSTEM SET "_disable_fast_validate"=TRUE SCOPE=BOTH SID= '*';

After you install the Oracle Beehive 2.0.1.7.0 Cumulative Patch Set, you can re-enable fast validation using the following commands:

ALTER SYSTEM RESET "_disable_fast_validate" SCOPE=SPFILE SID='*';
ALTER SYSTEM SET "_disable_fast_validate"=FALSE SCOPE=MEMORY SID='*';

Apply Database Patch 8440319 in Database Oracle Home

If you have not already done so (such as when applying a previous patch), apply the one-off patch for Oracle Database bug 8440319 (only for 11.1.0.7.0) in your Oracle Beehive database Oracle home before applying this patch set. Review the README in that patch after unzipping for instructions for applying the patch. Perform all post-patch steps as documented in that README. This Oracle Beehive patch will fail if the post-patch steps are not performed.

Patch Required for Upgraded Beehive Instances on Oracle Database 11.2

Bug 10134218. If you have upgraded your Oracle Database to 11.2, you may require a patch in order to successfully install the Oracle Beehive 2.0.1.7.0 Cumulative Patch Set.

If both of the following conditions are true:

  • You have patched from Oracle Beehive 2.0.1.2.0 to either 2.0.1.2.1 or 2.0.1.3.0

  • After performing the patch, you upgraded your Oracle Database from version 11.1 to 11.2

Then you must apply a special patch, else the Beehive 2.0.1.7.0 Cumulative Patch Set will fail during installation.


Note:

If you do not apply the required patch and you experience the failure during the Oracle Beehive 2.0.1.7.0 Cumulative Patch Set, you can still apply the 10134218 patch at that time, and then complete the 2.0.1.7.0 installation.

If you need to apply this special patch, contact Oracle Support to get the correct version of the 10134218 patch for your operating system and upgrade scenario.

Install Patch 7311226 on 11.1.0.7.x

If you are using Oracle Database 11.1.0.7.x, install patch 7311226 so that Oracle text index full optimization can resume where it left off on the next run. If you are using 11.2.x.x or higher, you do not need to install the patch.

Install Patch 13922299 on 11.2.0.3

If you are using Oracle Database 11.2.0.3, install patch 13922299 for Oracle Beehive search to work. This patch is required for any Oracle Beehive version using Oracle Database 11.2.0.3.

Installation


Note:

  • You must patch Oracle Beekeeper Oracle home(s) only after at least one Oracle Beehive Oracle home has been patched (using the -first_midtier option), and at least one instance of Oracle Beehive must be up and running when you apply the patch to Oracle Beekeeper.

  • Versions of Oracle Beekeeper without this patch set applied will not work with Oracle Beehive servers that have the 2.0.1.7.0 Cumulative Patch Set applied. You must patch Oracle Beekeeper before you can use it with a patched Oracle Beehive instance.


To install 2.0.1.7.0 Cumulative Patch Set for Oracle Beehive Release 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, or 2.0.1.6.0), perform the following steps on each Oracle Beehive server and Oracle Beekeeper Oracle home in your deployment:

  1. Make sure that the Oracle Beehive Database instance and TNS Listener are up and running. If any standby databases are defined, then make sure the standby databases listeners are stopped.

  2. If you are applying this Cumulative Patch on Oracle Beehive 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0,2.0.1.5.0, or 2.0.1.6.0, shut down all processes in the Oracle Beehive Application tier where the patch will be applied, before applying this patch set. Other Application tiers (including DMZ installations) can be up and running when applying the patch on a given Application tier. (Oracle Beekeeper instances must be shut down.)

    If you are patching an Oracle Beehive Coexistence Connector instance (any version), you must shut down all processes in the Coexistence Connector Oracle home before applying the patch.


    Note:

    This means that when updating from 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0 to 2.0.1.7.0, you can perform a rolling patch by patching one Application tier at a time, without shutting down your Oracle Beehive deployment. (You cannot use the rolling patch method when updating from any previous version.)

    Make sure that Oracle Beehive processes were gracefully started and all services were running before shutting down a given Application tier.


    Note:

    If you have not deployed Oracle Universal Records Management (URM), the Records Management Service will be disabled. You do not need to enable this service prior to patching.

    However, all other Oracle Beehive services must be enabled and running before you shut down your Oracle Beehive deployment, including services you may normally leave disabled, such as the Device Management Service.


  3. Unzip the downloaded package to a convenient location.

  4. On Linux and UNIX only, set your current directory to the directory where the patch is located. For example:

    % cd <directory_name>
    

    where, <directory_name> is the directory where the current patch is located.

    (You do not need to take this step on Windows.)

  5. If you are patching an Oracle Beehive server, set the ORACLE_HOME environment variable to your Oracle Beehive Oracle home. For example:

    On UNIX and Linux platforms:

    % setenv ORACLE_HOME /app/oracle/products/beehive
    

    On Windows:

    set ORACLE_HOME=C:\Beehive_Home
    

    If you are patching an Oracle Beekeeper instance, set the ORACLE_HOME environment variable to your Oracle Beekeeper Oracle home. For example:

    On UNIX and Linux platforms:

    % setenv ORACLE_HOME /app/oracle/products/2.0.1.7.0/beekeeper_1
    

    On Windows:

    set ORACLE_HOME=C:\Beekeeper_Home
    
  6. Use the following commands to apply the patch:

    • When applying the patch to the first Oracle Beehive (non-DMZ, non-Beekeeper, non-coexistence connector) instance, run the opatch command with the -first_midtier option:


      Note:

      Do not start with a DMZ instance. You must patch a non-DMZ instance first.

      When using RAC database with non-ASM configuration, if you want the patch to use only a particular node, you can provide the connect string for that node only in the below command (as the -dbconnstr value).


      % $ORACLE_HOME/OPatch/opatch napply -post -sys_passwd <sys password> -dbconnstr "(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db hostname>)(PORT=<db listen port>))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<db service name>)))" -first_midtier -opatch_post_end
      

      Note:

      On Windows, omit the double-quotes surrounding the value of -dbconnstr:
      patch.bat napply -post -sys_passwd <sys password>  -dbconnstr (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db hostname>)(PORT=<db listen port>))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<db service name>))) -first_midtier -opatch_post_end
      

    • When applying the patch to additional Oracle Beehive (non-DMZ, non-Beekeeper, non-coexistence connector) instances, run the opatch command without the -first_midtier option:

      % $ORACLE_HOME/OPatch/opatch napply -post -sys_passwd <sys password> -dbconnstr "(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db hostname>)(PORT=<db listen port>))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<db service name>)))" -opatch_post_end
      

      Note:

      On Windows, omit the double-quotes surrounding the value of -dbconnstr:
      patch.bat napply -post -sys_passwd <sys password> -dbconnstr (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db hostname>)(PORT=<db listen port>))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<db service name>))) -opatch_post_end
      

    • When applying the patch to a separate Oracle Beekeeper Oracle home.


      Note:

      • You must patch Oracle Beekeeper Oracle home(s) only after at least one Oracle Beehive Oracle home has been patched (using the -first_midtier option).

      • At least one Oracle Beehive instance must be up and running when you apply the patch set to Oracle Beekeeper. Oracle Beehive instances are automatically started after applying the patch. If you subsequently shut down patched instances, be sure to start up at least one patched instance before applying the patch to Oracle Beekeeper Oracle homes.

      • The command-line syntax for applying the patch is case sensitive.


      On UNIX and Linux:

      % $ORACLE_HOME/OPatch/opatch napply
      

      On Windows:

      patch.bat napply
      
    • When applying the patch to an Oracle Beehive DMZ instance Oracle home, use the following command:

      On UNIX and Linux:

      % $ORACLE_HOME/OPatch/opatch napply
      

      On Windows:

      patch.bat napply
      

      Note:

      After applying a patch, Oracle Beehive will attempt to restart a patched instance, including DMZ instances. However, if you have not yet performed the Update hasbind File Ownership post-installation step, a DMZ instance may be unable to use privileged ports. In this case, shut down the DMZ instance, and restart it after performing post-installation steps.

    • When applying the patch to an Oracle Beehive Coexistence Connector Oracle home, use the following command:

      On UNIX and Linux:

      % $ORACLE_HOME/OPatch/opatch napply -post -password <OC4J Admin Password> -opatch_post_end
      

      On Windows:

      patch.bat napply -post -password <oc4jadmin password > -opatch_post_end 
      

    The value of <oc4jadmin password> is the password initially entered for the OC4J admin account when you installed the Oracle Beehive Coexistence Connector in this deployment.

  7. Be sure to repeat all steps in this procedure on each Oracle Beehive server in your deployment.

Post-Installation Steps

After performing the installation, perform the steps in the following sections, where applicable:

Update hasbind File Ownership

On Linux and UNIX Oracle Beehive servers, if your $ORACLE_HOME/beehive/bin/hasbind file was owned by root (in order to use privileged ports) before applying this patch, be sure to change it back to ownership by the root user. For example, you could execute the following commands using an account with superuser privileges:

$ cd $ORACLE_HOME/beehive/bin
$ chown root hasbind
$ chmod a+x hasbind
$ chmod a+s hasbind

See Also:

For more information about the hasbind file and reasons for modifying it, see "Modifying Oracle Beehive Ports using Privileged Port Numbers" in Chapter 5, "Managing Oracle Beehive Services" in the Oracle Beehive Administrator's Guide.

Reset Fast Validation in the Database

After you install the Oracle Beehive 2.0.1.7.0 Cumulative Patch Set, you can re-enable fast validation using the following commands:

ALTER SYSTEM RESET "_disable_fast_validate" SCOPE=SPFILE SID='*';
ALTER SYSTEM SET "_disable_fast_validate"=FALSE SCOPE=MEMORY SID='*';

Run Perl Script post_upgrade_db_actions.pl

If, and only if, you installed this patch on Oracle Beehive 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0, since the patch involves schema cloning, you must run the post_upgrade_db_actions.pl script.

If you installed this patch on Oracle Beehive 2.0.1.2.0 or earlier, you do not need to run this script.


Note:

When you enter the <CONNECT_STRING> argument for the perl script, you must enclose it in double-quotes.

For complete instructions, see "Running Perl Script post_upgrade_db_actions.pl," in Chapter "Upgrading Oracle Beehive Overview" of the Oracle Beehive Installation Guide for your platform.

Starting with 2.0.1.7.0, after running the Perl script post_upgrade_db_action.pl, execute the following beectl command on all Beehive instances:

beectl modify_local_configuration_files

Run SQL Script uds_post_upgrade_seed.sql

Bug 9722573. After applying this patch, you must run a SQL script to clean up group membership data in UDS. Log in to your Oracle Beehive database using SQL Plus as the current BEE_CODE user, and run the script uds_post_upgrade_seed.sql. The script is located in the following folder:

BEEHIVE_HOME/beehive/tmp/patch/13361024/db

Gather Statistics about Oracle Beehive Data and Code Schemas

After upgrading to Oracle Beehive Release 2 (2.0.1.7) and before your users access your upgrade Oracle Beehive deployment, you must gather statistics about the Oracle Beehive data and code schemas. Else, you may experience serious performance degradation or service interruptions. To know how to gather statistics, refer the following link:

http://download.oracle.com/docs/cd/E16671_01/bh.200/e16641/upgrade_overview.htm#CJAEAJDC

Upgrade Inventory Version

After the patch is successfully applied, upgrade the inventory version of Oracle Beehive components:

  1. Navigate to the upgrade inventory script in the following location:

    <extracted_patch_location>/13361024/Beehive_20170/custom/scripts

  2. Extract the ZIP file containing a script to a folder on your local file system:

    • In Oracle Beehive instances, extract the files from the following .zip:

      BeehiveVersionUpgradeTo20170.zip
      
    • In Oracle Beekeeper instances, extract the files from the following .zip:

      BeekeeperVersionUpgradeTo20170.zip
      

    A subdirectory containing the script is created.

  3. Run the shell script as follows:

    • In Oracle Beehive instances:

      For Linux and UNIX:

      % BeehiveVersionUpgradeTo20170.sh <PATH_TO_ORACLE_HOME>
      

      or for Windows:

      % BeehiveVersionUpgradeTo20170.bat <PATH_TO_ORACLE_HOME>
      
    • In Oracle Beehive DMZ and Coexistence Connector instances:

      For UNIX and Linux:

      % BeehiveVersionUpgradeTo20170.sh <PATH_TO_ORACLE_HOME>
      

      or for Windows:

      % BeehiveVersionUpgradeTo20170.bat <PATH_TO_ORACLE_HOME>
      
    • In Oracle Beekeeper instances:

      For UNIX and Linux:

      % BeekeeperVersionUpgradeTo20170.sh <PATH_TO_ORACLE_HOME>
      

      or for Windows:

      % BeekeeperVersionUpgradeTo20170.bat <PATH_TO_ORACLE_HOME>
      

    Where <PATH_TO_ORACLE_HOME> is the path of the Oracle home (Oracle Beehive or Oracle Beekeeper) that you are upgrading

  4. Repeat steps 1 through 3 on all Oracle Beehive and Oracle Beekeeper instances whose inventories need to be updated to 2.0.1.7.0.

  5. To verify that the inventory on an instance has been updated, perform the following steps:

    1. Navigate to the following directory:

      % cd <Updated_Beekeeper_ORACLE_HOME>/oui/bin
      

      or

      % cd <Upgraded_Beehive_ORACLE_HOME>/oui/bin
      
    2. Start Oracle Universal Installer by invoking the runInstaller in this directory:

      % ./runInstaller
      

      or, on Windows:

      % setup.exe
      
    3. In the Oracle Universal Installer interface, click Installed Products. An inventory window will open.

    4. In the inventory window, you can see all of the Oracle home names on the current host. Expand your Oracle Beehive or Oracle Beekeeper name by clicking on the plus (+) just before it. Confirm that the version number is now Beehive Release 2 (2.0.1.7.0) or Oracle Beekeeper 2.0.1.7.0.

    5. To confirm the versions of other subcomponents, expand Oracle Beehive or Oracle Beekeeper 2.0.1.7.0 by clicking on the plus (+) just before it. Traverse through the list of subcomponents and confirm the following upgraded components:

      On Oracle Beehive:

      Oracle Beehive Release 2 Configuration 2.0.1.7.0 
      Oracle Beehive Release 2 Database Support 2.0.1.7.0 
      Oracle Beehive Release 2 Binaries 2.0.1.7.0 
      Oracle Beehive Release 2 Libraries 2.0.1.7.0 
      Oracle Beehive Release 2 Services 2.0.1.7.0 
      Oracle Beehive Release 2 Configuration Wizard 2.0.1.7.0 
      Oracle Commuication and Messaging Services 2.0.1.7.0
      Oracle Beehive Release 2 Oneoffs 2.0.1.7.0
      

      On Windows, also confirm:

      Oracle Collaboration Coexistence Gateway 2.0.1.7.0
      

      On Oracle Beekeeper:

      Oracle Beekeeper 2.0.1.7.0
      Oracle Beekeeper OC4J 2.0.1.7.0
      Oracle Beehive Release 2 Oneoffs 2.0.1.7.0
      Oracle Beehive Release 2 Configuration Wizard 2.0.1.7.0
      

Search Service Post-Installation Configuration

The Oracle Beehive 2.0.1.3.0 Cumulative Patch (which is included in this cumulative patch set) included a refactoring of the Oracle Beehive Search Service. This is a substantial change which may require additional post-configuration steps in the following areas:

Building a New Search Index of Existing Artifacts

If you installed this patch on Oracle Beehive 2.0.1.2.0 or earlier, the existing search index is erased during patching. As a result, after the upgrade any search operation on existing data will return no results.

If you installed this patch on Oracle Beehive 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0 and used the Zero Downtime Upgrade (ZDU) method, search indexing is suspended during the patching process. Changes in the system that occurred during patching are not indexed.

You can build a new search index of existing artifacts, using a new beectl command, beectl add_search_recovery_scope:

beectl add_search_recovery_scope 
  --scope <recovery_scope> 
  [--entity_type <entity_type>]
  [--start_date <start_date>]
  [--end_date <end_date>]

Where:

  • <recovery_scope> is the identifier for a level of scope for the utility to crawl for indexing, such as enterprise, organization, workspace, or folder.

  • <entity_type> indicates searchable entity types. You can specify this option more than once to indicate multiple entities types to index. If you omit this option, all entity types are searched and indexed.

  • <start_date> recovers search index for entities modified on or after this date. If not specified, 30 days before the present will be used as the start date. Permitted value is a string in ISO8601 date-time format. Valid formats are yyyy-MM-dd'T'HH:mm:ss.SS'Z', yyyy-MM-dd'T'HH:mm:ss.SS, yyyy-MM-dd'T'HH:mm:ss'Z', yyyy-MM-dd'T'HH:mm:ss, yyyy-MM-dd'Z', yyyy-MM-dd.

  • <end_date> recovers search index for entities modified before or on this date. If not specified, the present will be used as the end date. Use the same format as for <start_date>.

As soon as you issue an add_search_recovery_scope command, Oracle Beehive starts the background work and immediately returns an operation ID. You can use the operation ID with the beectl list_operation_statuses command to track the progress of the recovery job.

beectl list_operation_statuses --operation_status 1CF3:35AF:opst:6828B43CD3944E06A5CD425F0225CF2500000000004C

The add_search_recovery_scope command will immediately add a list of all artifacts identified by the run time options to a queue of items to be indexed. Adding too many items to this queue at once will slow down the system. Oracle recommends reviewing the Recovery Crawler section of Oracle Support Note 1135054.1 prior to running the command.

To minimize performance impact, consider the following strategies:

  • Run the recovery crawler command during off-peak hours

  • Create a batch file to recover a few personal or team workspaces or a few days of email data at a time

  • Monitor the SS_FEEDS load (information in Oracle Support Note 1135054.1)

Configuring Oracle Secure Enterprise Search (SES) Integration

If you are using Oracle Secure Enterprise Search (SES) with Oracle Beehive, if you have not already done so (such as after installing the 2.0.1.2.1, 2.0.1.3.0, 2.0.1.4.0, 2.0.1.5.0, or 2.0.1.6.0 patch set) you must take additional steps to configure SES integration. The following procedure provides a high-level outline of the actual configuration steps. For complete instructions, see MetaLink Note 1135054.1.

Perform the following steps to configure SES integration:

  1. Perform the complete procedure for basic SES integration as detailed in Chapter 10, "Integrating Oracle Secure Enterprise Search 10g with Oracle Beehive" of the Oracle Beehive Integration Guide.

  2. If needed, configure your Identity Management solution with the appropriate host, port, realm, and other connection settings.

  3. If needed, create source groups (groupings of data sources, which appear as tabs above the search box).

  4. From the SES Admin console, set up a title URL for Oracle Beehive search results by creating new search attributes, and then modifying the XSL stylesheet to include the new attributes.

  5. From the SES Admin console, add Oracle Beehive search result attributes and filtering attributes.

Deploy the JavaFX Runtime in the DMS

Beehive Conferencing introduced a new Java-based architecture that can be used by end users without requiring any Operating System-specific desktop installation. One of the many advantages of this new architecture is the ability to leverage Java to auto-detect, auto-install, and auto-update all the necessary components required by Beehive Conferencing to run. Therefore, for a user to join a conference, the Beehive Conferencing application needs to access the following resource:

  • JavaScript code (deployJava.js) for launching Java applications and detecting JRE versions.

Out of the box, Beehive Conferencing uses the "official" versions of these files by accessing the file through the java.com site over the web. This can cause some issues if a user doesn't have access to the internet, can't access the java.com site (for example, it is unavailable at that time), and/or does not have their proxy settings configured correctly.


Note:

Oracle recommends that you deploy the JavaFX Runtime in the Beehive DMS. For details see Chapter 28, "Installing Oracle Beehive Conferencing Client" of the Oracle Beehive Installation Guide, Release 2.0 at the following link: http://www.oracle.com/pls/bee2/homepage

Resolved Issues

Table 2, "Resolved Issues in Oracle Beehive 2.0.1.7.0 Cumulative Patch Set" lists the issues resolved in this patch set.

The issues that were resolved by the Oracle Beehive 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, and 2.0.1.6.0 patch sets (and are included in this cumulative patch) are listed in detail in the patch readmes for each patch. You can find the readmes on the Oracle Technology Network Web site, at the following URLs:

Table 2 Resolved Issues in Oracle Beehive 2.0.1.7.0 Cumulative Patch Set

Defect Number Description

Beehive Conferencing

12766555

Windows and Mac OS – When presenting an application, there is a grey background layer behind the mini console.

12905453

If a host is disconnected while presenting, then when connection is re-established, the presenter is still in presenter console/mode but is no longer presenting. The presenter needs to restart the presentation by clicking Stop presentation or Change presentation to be able to present again.

13098142

Unable to view the presentation using the Conferencing Java-based client. The read buffer size needs to be increased to avoid this issue.

13114140

When attempting to connect to a pre-scheduled Beehive Web Conference through Web, user gets the following error: Failed to initialized presentation libraries.

13243143

Presentation corruption when switching to full screen and back. Corruption of display in Java-based Conferencing clients when a Windows client presents full screen applications.

13344833

Starting and stopping a presentation multiple times causes connection loss or crash in the Java-based Conferencing client.

13346092

When trying to launch a Beehive conference in Google Chrome 15, the user is prompted to discard or save the oraclebeehiveconferencing.jnlp file. If the file is saved and opened manually, the conference is launched the first time. But subsequently, the conference silently fails to launch due to a conflict with the previous (same name) .jnlp file.

13348807

Lost presentation and crash after several presentation changes. The Java-based Conferencing client loses presentation content and crashes sometimes with frequent presentation changes from the presenter.

Oracle Beehive Extensions for Outlook

13431048

Oracle Beehive Extensions for Outlook login dialogue with default focus on host name field instead of the password field.

13698306

Meetings not created in Oracle Beehive Extensions for Outlook do not have 'Propose new time' enabled.

Oracle Beehive Extensions for Explorer

13689177

Oracle Beehive Extensions for Explorer login dialogue with default focus on host name field instead of the password field.

Patch

13352810

Opatch failed since it could not connect to standby database instance.

Services

11072043

Users in enabled state in Oracle Beehive without any visible workspace and two deleted workspaces.

12316068

Ability to sync the working hours from Oracle Beehive Extensions for Outlook and TM-service (Oracle Beehive Central).

12779679

In Beekeeper and documentation, the description about the Use default max email size is erroneous.

13084381

Rescheduled instance of recurring meeting are ignored when rescheduled using iPhone.

13098130

When exporting a workspace with a blank Wiki page, the export_workspace command hangs at 5% - one CPU pinned at 100%.

13112874

iPhone iOS 5 Reminders application Todo with location based reminders not supported.

13388132

Windows7: When trying to save an Office 2010 document opened via webdav in a team workspace, an error is displayed that the document is locked by another user.

13486510

The beectl command validate_directory_entry does not properly report change in external inbox value.

13545062

Calendar events created using Oracle Beehive Extensions for Outlook with external customers off by 65 mins.

13627293

When the download_ldap_user_data command is run in SSL mode, wrong service instance type error is returned.

13960624

When attempting to re-index users workspaces following the post install instructions for Beehive patch, the beectl add_search_recovery_scope command returns a 'Search SQL' error.

14063905

When attempting to re-index users workspaces following the post install instructions for Beehive patch, the beectl add_search_recovery_scope command returns an 'Inserted value too large for column' error.

Oracle Beehive Team Collaboration

13610666

Blank space in URL was causing an error when rendered in a Beehive wiki page.

Oracle Beehive Webmail

12755327

Re-occurring workspace's calendar events not displayed by Oracle Beehive Webmail.

12933189

Workspaces with leading numbers in the title cannot be seen using Oracle Beehive Webmail client.

13359824

New contact group from Oracle Beehive Webmail loses contacts after re-login.

13415885

Oracle Beehive Webmail contact group empty after logout.

13539826

Unable to process workflow tasks via Oracle Beehive Webmail.

13609912

Split (GMT+05.00) Islamabad/Karachi/Tashkent into two different timezones in Oracle Beehive Webmail – (GMT+5.00 Islamabad/Karachi) and (GMT+5.00 Tashkent).

13984261

Oracle Beehive Webmail UI shows a dummy link after adding 52 shared calendars.

14035682

Other user's calendar links missing from Oracle Beehive Webmail client.


Known Issues

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


2.0.1.7.0 Cumulative Patch Set for Oracle Beehive Release 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, and 2.0.1.6.0)

Copyright © 2008, 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.