Skip Headers

Oracle® Beehive 2.0.1.2.0 Cumulative Patch Set Readme
For Oracle Beehive Release 2 (2.0.1.0.0 and 2.0.1.1.0) (All Platforms)
 

 

Oracle® Beehive

2.0.1.2.0 Cumulative Patch Set Readme

For Oracle Beehive Release 2 (2.0.1.0.0 and 2.0.1.1.0) (All Platforms)

May 2010

Readme updated June 25, 2010

This Readme accompanies 2.0.1.2.0 Cumulative Patch Set for Oracle Beehive Release 2 (2.0.1.0.0 and 2.0.1.1.0).

This option installs 2.0.1.2.0 Cumulative Patch Set, for installations of Oracle Beehive Release 2 (2.0.1.0.0 and 2.0.1.1.0) only. Before applying this patch, you must upgrade your Oracle Beehive Release 1 deployment to Release 2 (2.0.1.0.0). Do not attempt to install this patch set on earlier versions of Oracle Beehive.

Instead of using this Patch Set, you may be able to upgrade your Oracle Beehive installation using the Oracle Universal Installer (OUI) method. Table 1, "Oracle Beehive Upgrade Options for 2.0.1.2.0" shows the upgrade and patch options that are available.

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

  • Patch to 1.5.1.5.0, then use 2.0.1.2.0 OUI installer

  • Upgrade to 2.0.1.0, then use 2.0.1.2.0 Cumulative Patch Set

1.5.1.5.0, 1.5.1.5.1, or 1.5.1.5.2

Either:

  • Use 2.0.1.2.0 OUI installer

  • Upgrade to 2.0.1.0.0, then use 2.0.1.2.0 Cumulative Patch Set

2.0.1.0.0, 2.0.1.1.0

You must patch using 2.0.1.2.0 Cumulative Patch Set only. You cannot use the 2.0.1.2.0 OUI installer.

This Readme contains the following topics:

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/ .

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/support/contact.html or visit http://www.oracle.com/accessibility/support.html if you are hearing impaired.

Introduction

This Readme includes information on installation, important notes, and known workarounds for the Oracle Beehive 2.0.1.2.0 Cumulative Patch Set for Oracle Beehive Release 2 (2.0.1.0.0 and 2.0.1.1.0).

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

Important Notes

Please review the following important notes before installing this patch:

Installation with Oracle Enterprise Manager Not Supported

Applying 2.0.1.2.0 Cumulative Patch Set using Oracle Enterprise Manager is not supported.

ROLLBACK Not Supported

ROLLBACK of this patch is not supported. If you need to undo a partial or complete installation of this patch, you must restore Oracle Beehive and the database from backup.

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 website, at the following URL:

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

Oracle Beekeeper Patch May Not Exit After Patching on Windows

Bug 9530414. Due to a problem with the Windows version of Oracle Beekeeper patch set installation, the patch set may appear to freeze or hang after completion without exiting. If you see the message "Beehive Upgrade completed," but the patch set does not subsequently exit, open a new command shell in the Oracle Beekeeper Oracle home, and run the following command:

opmnctl stopall

This will end the patch set installer process.

New EmailService:CSIProperties Property Introduced

The 2.0.1.1.0 Patch Set (which is included in this Cumulative Patch Set) adds a new property to the EmailService:CSIProperties component. The new VMSProperties property stores the name of a virtual mail server (VMS) (by default, the OutboundVMS). Oracle Beehive will apply the limits on message size and recipient count stored as part of that VMS, to all Beehive-internal (CSI) e-mail messages sent from Oracle Beehive clients, such as Oracle Beehive Webmail and OBEE.

This allows you to configure maximum message size and maximum recipient count for your entire Oracle Beehive deployment in one place (the OutboundVMS), and those limits will apply to all e-mail traffic.

Oracle Beehive Webmail Experience Issue After Patching

As a result of fixing Bug 9076147, after you apply 2.0.1.2.0 Cumulative Patch Set, Oracle Beehive Webmail users may be immediately logged out with a session timeout error the first time they log in.

Users can either delete their browser cache before attempting to log in, which will avoid the issue, or log out and then log in again.

Installation Issue on French-Localized Windows Server 2003

Bugs 9661710, 9782475. Due to a bug, Oracle Beehive 2.0.1.2.0 Cumulative Patch Set (and certain previous patch sets) may fail while applying one-off patches, on Windows Server 2003, French edition, on a system which has been previously upgraded or patched. The patch log includes an error similar to the following:

INFO:sInstallTime = >2010.May.26 22:25:58 ACT<
INFO:java.text.ParseException: Unparseable date: "2010.May.26 22:25:58 ACT"

The problem occurs because the ACT time zone is erroneously set by a previous patch, and Opatch does not recognize this time zone. You can correct this error and complete your upgrade by modifying the following file:

<Beekeeper_HOME>/inventory/ContentsXML/comps.xml.

Open the file in an editor and change all instances of the time zone designation from ACT to a different time zone, such as GMT or PST. After you save and close the file, you can run the opatch utility and the patch should succeed.

RIM Blackberry attachment corruption

Bug 9674377. On the RIM Blackberry mobile client, Non-ASCII data in text attachments to e-mails delivered to Blackberry clients may become corrupted

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 or 2.0.1.1.0) Only

Oracle Beehive 2.0.1.2.0 Cumulative Patch Set can only be installed on Oracle Beehive Release 2 (2.0.1.0.0 or 2.0.1.1.0). 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.2.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

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.

Shut Down Oracle Beehive

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.

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

Install Database Patches on Oracle Database 11.1.0.7.x

There are two required database patches for certain versions of Oracle Database 11.1.0.7.

Patch 8440319

If you are using Oracle Database 11.1.0.7.x, you must install a database patch before installing Oracle Beehive 2.0.1.2.0 Cumulative Patch Set. (You can skip this step if you previously installed this database patch while applying the Oracle Beehive 2.0.1.1.0 Patch Set.)


Note:

You do not need to perform this step if you are using Oracle Database 11.2.

Download the Oracle Database patch for Bug 8440319 to your Oracle Database Oracle home. Extract the archive, and follow the instructions in the included README.txt to install the patch. After applying the patch, be sure to follow the post-installation steps in the readme.

If you do not install this database patch, the 2.0.1.2.0 Cumulative Patch Set installation will fail.

Patch 9434549

If you are using Oracle Database 11.1.0.7.2, you must install a database patch before installing Oracle Beehive 2.0.1.2.0 Cumulative Patch Set.

Download the Oracle Database patch for Bug 9434549 to your Oracle Database Oracle home. Extract the archive, and follow the instructions in the included README.txt to install the patch. After applying the patch, be sure to follow the post-installation steps in the readme.

If you do not install this database patch, the 2.0.1.2.0 Cumulative Patch Set installation will fail.

Disable Fast Validation in the Database

You must disable fast validation in the database before installing Oracle Beehive 2.0.1.2.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.2.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='*';

On Solaris, Perform Workaround

Bug 9237090. Due to a database bug, Oracle Beehive search functions on deployments in Solaris environments will fail after applying this patch set unless you perform a workaround. Before applying this patch set, perform the following steps:

  1. On the Solaris database server, update the LD_LIBRARY_PATH:

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/ctx/lib
    

    Note:

    If you later perform any database operation that could reset the LD_LIBRARY_PATH, you must run this command again to ensure the $ORACLE_HOME/ctx/lib folder is included in the path.
  2. Update the listener.ora as follows, substituting appropriate values:

    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
           (ADDRESS = (PROTOCOL = TCP)(HOST = dbhost.example.com)(PORT =
    1521))
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
        )
    
    (ENVS="LD_LIBRARY_PATH=/usr/lib:/usr/dt/lib:/usr/openwin/lib:/opt/SUNWspro/lib
    :/usr/ccs/lib:opt/app/oracle/product/beehive/db11g/ohome/ctx/lib")
      )
    
  3. Restart the database listener and the database

When Upgrading Oracle Beekeeper Which has Previously Been Upgraded from 1.5.1.x to 2.0.1.0.0 Perform Workaround

Bug 9444973. If you have previously upgraded your Oracle Beekeeper instance from version 1.5.1.x to 2.0.1.0.0, you must perform the following workaround before you can apply 2.0.1.2.0 Cumulative Patch Set.

After extracting the 2.0.1.2.0 Cumulative Patch Set, navigate to the following directory:

$ORACLE_HOME/.patch_storage

Then, extract the following file:

<patch_extracted_location>/9443518/Beehive_2012/custom/scripts/beepatch/9041410_workaround.zip

Once you have extracted 9041410_workaround.zip, you can apply 2.0.1.2.0 Cumulative Patch Set to your Oracle Beekeeper Oracle home.

Perform Workaround when Patching Coexistence Connector for Exchange

Both the Coexistence Connector for Exchange patch, and upgrade flows, require manual steps when patching from Oracle Beehive 2.0 (2.0.1.0.0 or 2.0.1.1.0) to 2.0.1.2.0.


Caution:

Perform the following workaround when updating a previous CNS only installation, or a previous Coexistence Connector plus CNS installation. You MUST NOT perform this procedure on a Coexistence Connector-only installation.

This workaround is not needed on Oracle Beehive Coexistence for Domino installations.

To apply the workaround, perform the following steps:

  1. Extract the 2.0.1.2.0 Cumulative Patch Set and navigate to the Beehive_2012\custom\scripts\beepatch directory

  2. Extract the Beehive_9443518.zip file into a temporary directory

  3. Copy the files under \collabcoex_connector to $ORACLE_HOME\beehive\collabcoex_connector

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

    Note:

    Optionally, you may omit the --admin_password option. You will be prompted to enter the password when you run the command.
  5. You can now apply 2.0.1.2.0 Cumulative Patch Set according to the instructions in the Installation section.

Installation


Notes:

  • 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.2.0 Cumulative Patch Set applied. You must patch Oracle Beekeeper before you can use it with a patched Oracle Beehive instance.

  • Oracle Beekeeper instances that were previously upgraded from version 1.5.1.x to 2.0.1.0.0 must have a special patch applied before upgrading to 2.0.1.2.0. See the Oracle Beekeeper installation step for details.

To install 2.0.1.2.0 Cumulative Patch Set for Oracle Beehive Release 2 (2.0.1.0.0 and 2.0.1.1.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.

  2. Shut down all processes in all Oracle Beehive Application tiers, including Coexistence Connectors and DMZ instances.

    Make sure that Oracle Beehive processes were gracefully started and all services were running before shutting down the Application tiers for patching.


    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. Set your current directory to the directory where the patch is located. For example:

    % cd 9443518
    
  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.0.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 instance, run the opatch command with the -first_midtier option:


      Notes:

      • Do not start with a DMZ instance. If your deployment includes DMZ instances, patch them using the "additional Oracle Beehive instances" step, without the -first_midtier option.

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


      Caution:

      Previously-upgraded instances of Oracle Beekeeper require a special patch before they can be upgraded to 2.0.1.2.0. If you skip this step, Oracle Beekeeper will not be upgraded properly.

      If you previously upgraded this Oracle Beekeeper instance from version 1.5.1.x to 2.0.1.0.0, navigate to the following directory:

      $ORACLE_HOME/.patch_storage
      

      From here, extract the following file:

      % unzip <patch_extracted_location>/9443518/Beehive_2012/custom/scripts/beepatch/9041410_workaround.zip
      

      After extracting the file to your Oracle Beekeeper instance, you can then proceed with the 2.0.1.2.0 upgrade:


      Notes:

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


      Note:

      Bug 9530414. Due to a problem with the Windows version of Oracle Beekeeper installation, the patch set may appear to freeze or hang after completion without exiting. If you see the message "Beehive Upgrade completed," but the patch set does not subsequently exit, open a new command shell in the Oracle Beekeeper Oracle home, and run the following command:
      opmnctl stopall
      

      This will end the patch set installer process.

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


      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.

      On UNIX and Linux:

      % $ORACLE_HOME/OPatch/opatch napply
      

      On Windows:

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

      % 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.2.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='*';

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>/9443518/Beehive_2012/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 for your operating system:

      Beehive_2012/custom/scripts/BeehiveVersionUpgradeTo20120_linux.zip
      Beehive_2012/custom/scripts/BeehiveVersionUpgradeTo20120_sol.zip
      Beehive_2012\custom\scripts\BeehiveVersionUpgradeTo20120_win.zip
      
    • In Oracle Beekeeper instances, extract the files from the following .zip for your operating system:

      Beehive_2012/custom/scripts/BeekeeperVersionUpgradeTo20120_linux.zip
      Beehive_2012/custom/scripts/BeekeeperVersionUpgradeTo20120_sol.zip
      Beehive_2012\custom\scripts\BeekeeperVersionUpgradeTo20120_win.zip
      

    A subdirectory will be created containing the script

  3. Run the shell script as follows:

    • In Oracle Beehive instances:

      For Linux and UNIX:
      % BeehiveVersionUpgradeTo20120.sh  
                                                  
      <PATH_TO_ORACLE_HOME>
      or for Windows: % BeehiveVersionUpgradeTo20120.bat
      <PATH_TO_ORACLE_HOME>
    • In Oracle Beehive DMZ and Coexistence Connector instances:

      For UNIX and Linux:
      % BeehiveVersionUpgradeTo20120.sh  
                                                  
      <PATH_TO_ORACLE_HOME>
      or for Windows: % BeehiveVersionUpgradeTo20120_DMZ_COEX.bat
      <PATH_TO_ORACLE_HOME>
    • In Oracle Beekeeper instances:

      For UNIX and Linux:
      % BeekeeperVersionUpgradeTo20120.sh  
                                                  
      <PATH_TO_ORACLE_HOME>
      or for Windows: % BeekeeperVersionUpgradeTo20120.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.2.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.2.0 or Oracle Beekeeper 2.0.1.2.0

    5. To confirm the versions of other subcomponents, expand Oracle Beehive or Oracle Beekeeper 2.0.1.2.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.2.0
      Oracle Beehive Release 2 Database Support 2.0.1.2.0
      Oracle Beehive Release 2 Binaries 2.0.1.2.0
      Oracle Beehive Release 2 Libraries 2.0.1.2.0
      Oracle Beehive Release 2 Services 2.0.1.2.0
      Oracle Beehive Release 2 Configuration Wizard 2.0.1.2.0
      Oracle Commuication and Messaging Services 2.0.1.2.0
      Oracle Beehive Release 2 Oneoffs 2.0.1.2.0
      

      On Windows, also confirm:

      Oracle Collaboration Coexistence Gateway 2.0.1.2.0
      

      On Oracle Beekeeper:

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

Resolved Issues

Table 2, "Resolved Issues in Oracle Beehive 2.0.1.2.0 Cumulative Patch Set" lists the issues resolved in this Patch Set (new for 2.0.1.2.0 Patch Set).

The issues that were resolved by the Oracle Beehive 2.0.1.1.0 patch set (and are included in this cumulative patch) are listed in detail in the patch readme for that patch. You can find the 2.0.1.1.0 readme on the Oracle Technology Network Website, at the following URL:

http://www-content.oracle.com/technetwork/middleware/beehive/overview/beehive-20110-readme-167644.html

Table 2 Resolved Issues in Oracle Beehive 2.0.1.2.0 Cumulative Patch Set

Bug Number Description

9326635, 9396256, 9432075, 9436001, 9440915, 9452234, 9455522, 9455574, 9459643, 9464444, 9464444, 9467740, 9467779, 9470451, 9480127, 9482872, 9484207, 9491435, 9501550, 9501571, 9501594, 9501629, 9501656, 9506234

Various performance issues were identified and fixed.

8976674

A problem in OBEO with syncronizing folder changes at the root level between multiple instances was identified and fixed.

9007699

In OBEO, improvements were made in how the client handles poor network performance during attachment uploads over MX

9094943

In the Team Collaboration client for Mac OS X, after entering an incorrect password, the client denied authorization even when a user subsequently entered the correct password.

9094959

In conferences initiatied using the Team Collaboration client for Mac OS X, the voice and recording buttons were not shown.

9130996

Under certain conditions, the beectl add_client_application_provisioning command failed inappropriately with the error ORA-06532: Subscript outside of limit.

9175815

An 'Open' resource could not be double-booked once an invitation to one of the bookings was accepted.

9176521

In OBEO, reminders were being created on meeting invitations in the Sent Items folder.

9193373

In the Team Collaboration client for Mac OS X, when a user connected using the non-secure port and created a meeting, the guest join URL displayed for the meeting incorrectly used the HTTPS protocol.

9220938

Oracle Beekeeper and WebLogic stand-alon servers could not be started successfully if no Oracle Beehive servers were running.

9231047

Under certain conditions, fewer than the maximum number of displayable calendar events were initially displayed in Mozilla Thunderbird with Mozilla Lightning.

9233953

A deadlock condition in the Mobile Data Sync Service was identified and fixed.

9305323

After updating viewing or delegation permissions for a calendar, changes were not propagated to events downloaded by delegatees using standards-based (CalDAV) clients.

9309279

In the Team Collaboration client for Mac OS X, after a long idle period in a meeting, the client could become unresponsive.

9324023

After restarting the Virus Scan Engine, e-mails were not delivered until the BEEAPP OC4J component was restarted.

9339076

Oracle Beehive now processes and delivers large numbers of simultaneous event reminder notifications more efficiently.

9360865

In the Workspaces client on Internet Explorer 7, the wiki page calendar plugin header text fields were resized so that they do not wrap to a second line.

9364420

Several improvements were made in the documentation of Predicate classes in the Beehive Developer's Kit (BDK).

9373491

The 'welcome' message sent when a user joins a workspace now shows the workspace owner or contact.

9388652

Instant messages sent to a RIM Blackberry client while it was offline were not delivered after reconnection.

9388942

In the Mozilla Lightning client, after dismissing an alarm for a recurring event, the next alarm for that event could not be dismissed.

9391807

In the Workspaces client, when a user attempted to upload a file with the same name as an existing file on the server, instead of prompting to overwrite the existing file, an error message was displayed.

9391867

In the Team Collaboration client for Mac OS X, after starting or joining a conference, attempting to open the conference details caused the client to become unresponsive.

9392418

In OBEO, some types of recurring meetings disappeared shortly after being downloaded and displayed.

9396137

The Device Managment Service was tuned to consume less CPU during certain operations.

9397084

In Oracle Webmail, after deleting a contact, the list of contacts paginated incorrectly.

9397391

In the Workspaces client, if the first preferred language setting (in the browser) is not supported, the client always defaulted to English instead of a supported second-preferred language.

9397436

In the Workspaces client, there was a display problem with text near bullet points in wiki pages.

9403452

In Lotus Domino coexistence deployments, under certain circumstances, a null pointer exception occurred which prevented the beectl list_coexistence_profiles command from working.

9403821

The beectl list_external_contacts command failed when there were a very large number (hundreds of thousands) of external contacts.

9407972

Because of a problem in Oracle Universal Content Manager (UCM), after copying a file from a folder using OBEE to a UCM folder, subsequent operations on any content in that folder using OBEE failed.

9412120

After deleting and purging a user account, and then re-creating a user with the same name, incompletely removed workspaces owned by that user caused IMAP configuration issues.

9430909

A deadlock condition in the Time Managment Service was detected and fixed.

9434401

In the Workspaces client, the file uploader now displays a progress bar, and the client better handles very large file uploads.

9434402

An error in the Mobile Data Sync Service was causing the BEEAPP component to consume excessive memory.

9438069

A new Beehive Time Zone package is included, containing updates from the Olson 2010E package.

9438338

In OBEO, attempting to convert a recurring day event to a regular recurring meeting caused an error.

9439019

Instant Messaging and Presence issues in the 2.0.1.1.0 Beehive SDK were resolved.

9439515

Intelligent Collaboration was failing to index terms containing the apostrophe (') character.

9439751

A performance optimization to e-mail stream reading was implemented, improving overall server performance.

9442449

Workspace welcome notification e-mails were being sent with the 'low' priority. They are now sent with normal priority.

9442672

OBEO was sending meeting cancellation notification e-mails directly. These messages will now be sent by the Beehive server.

9442780

Under certain circumstances, e-mail search for items using very long strings (but still within the upper limit for length) sometimes failed.

9446662

A deadlock condition in the Mobile Data Sync Service was detected and fixed.

9447458

In OBEO, a number of changes and improvements were made to upload error handling, error messages, progress indicators when the server is slow to respond, and other notifications.

9448057

A problem with IMAP message IDs caused the mobile mail application on Google Android devices to continuously retry saving draft and sent messages.

9448254

A problem with the default configuration of the second VMS evaluator in Oracle Beekeeper could cause e-mail routing to break if it was enabled.

9448459

In the Team Collaboration client Wiki pages, an equal sign (=) at the end of a heading could be duplicated when the page was saved.

9449955

In the Team Collaboration client, the 'Ongoing and upcoming conferences' link in the breadcrumbs wrapped onto a second line.

9451098

In OBEO, IMIP meeting requests are now handled by the client as meeting-requests, updates, or cancellations. Previously, these were shown as message attachments in the Inbox.

9451364

Intelligent Collaboration was including user names as matching terms in topics, even though they were on the stop words list.

9451860

A number of new statistics are added for the Email Service.

9455080

A problem caused out of memory crashes during Lotus Domino coexistence user free/busy processing.

9457419

The delay between new content added to a workspace, and the used quota of the workspace being updated, was too long, making it more likely that a user could exceed quota with rapid small uploads.

9463935

The Mobile client for RIM BlackBerry was not correctly displaying 503 (server busy/server unavailable) errors.

9464491

Oracle Beehive has added the ability to accept or decline meeting invitations from external sources as if they were internal invitations.

9467765

In the Mac OS X Conferencing client, the conference key in the join URL for an ad-hoc conference was incorrect, preventing guest users from using it to join.

9468414

In the Mac OS X Conferencing client, the join URL generated when a conference was started from the client contained null strings, making it unusable.

9472654

E-mail messages sent to external users containing a comma (,) in the display name did not surround the display name with quotes, which could cause problems when the message was parsed.

9475957

There was a problem with synchronizing messages in Coexistence envorinments.

9476161

In OBEO, the default number of results returned by the server when searching the Global Address List has been increased from 20 to 100. This value is now stored in a profile.ini key.

9476869

In Intelligent Collaboration, connection requests were by default excluding terms set by their owners to public. The default behavior is now to include such terms.

9477025

OBEO users can now re-download an individual meeting when it is not available locally, rather than having to refresh the entire calendar folder.

9478870

The Notification Delivery Service could run out of 6-digit action ID values, resulting in a loop that causes high CPU usage. The service now uses a larger action ID.

9483026

Unhandled exceptions during retry operations caused e-mail messages that required retries to sometimes become stuck in the queue.

9483442

In Oracle Beekeeper e-mail configuration, unchecking 'use sender matcher' or 'use recipient matcher' in any of the VMSes could cause the E-mail Service to fail.

9486830

A new beectl command to display the number of active CMS sessions was added.

9488509

The new Large Server deployment template inadvertently excluded the Syndication Service.

9488565

The site property OmbConnectOnDemand provides significant OMB performance optimization and is now enabled by default.

9490778

The Time Management Service was not properly handling available hours in free/busy when the work week was set as Monday to Sunday, such as in Beehive Central.

9491873

The Windows Conferencing client could not join conferences with large numbers (over fifty) of attendants.

9492102

The process for provisioning Oracle Beehive iPhone applications has been improved, and better information is provided to users during the process.

9493355

E-mails sent from Oracle Beehive to external recipients will now include the sender's display name in addition to their e-mail address in the headers in OBEO.

9497299

In Oracle Beehive Extensions for SharePoint (OBES), when a user clicks on the details for a user in a received connections request, if a WebParts profile exists, those details will be now be shown, instead of Beehive user account details.

9497430

Multi-part e-mail messages sent from Apple iPhones were missing final boundary markers, which Oracle Beehive could not parse correctly. Beehive can now handle such messages.

9498206

In Oracle Beehive Extensions for SharePoint (OBES), on the My Site page, clicking on the terms in the My Interests and Expertise webpart will now launch the search dialog.

9501506

The CalDAV directory cache has been tuned to scale better with large deployments.

9501611

The Coexistence Connector for Exchange now better handles batched simultaneous processing in CNS.

9501737

Coexistence Service logging has been improved.

9546429

To fix a bug caused by an earlier version, Oracle Beehive Webmail was updated to use NekoHTML 1.9.14.

9576638

OBEO upgrades where the old version was localized and the new was not, could cause some install messages to disappear.

9608532

On the Apple iPhone mobile client, the registration page on certain localized versions showed the phone number label overlapping with the phone number.

9654797

Due to a problem in Oracle Beehive Coexistence for Lotus Domino, a certain request from the Domino server went into a loop of retrying repeatedly.

Globalization Issues

2.0.1.2.0 Cumulative Patch Set for Oracle Beehive Release 2 (2.0.1.0.0 and 2.0.1.1.0) is available in English only. There are no translations of any English labels and other text.


2.0.1.2.0 Cumulative Patch Set for Oracle Beehive Release 2 (2.0.1.0.0 and 2.0.1.1.0)

Copyright © 2008, 2010, 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 software or related documentation 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 RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software 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 which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software 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.


 

Copyright © 2008, 2010, Oracle and/or its affiliates. All rights reserved.
 
Left Curve
Popular Downloads
Right Curve
Untitled Document
Left Curve
More Middleware Downloads
Right Curve