Oracle® Beehive

Table 1 Oracle Beehive Upgrade Options for 2.0.1.2.0

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.

opmnctl stopall

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

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

Installation Requirements

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

• Install on Oracle Beehive Release 2 (2.0.1.0.0 or 2.0.1.1.0) Only

• Backup your Oracle Beehive Deployment

• Install on All Oracle Beehive Application Tiers

• Shut Down Oracle Beehive

• Install Database Patches on Oracle Database 11.1.0.7.x

• Disable Fast Validation in the Database

• On Solaris, Perform Workaround

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

• Perform Workaround when Patching Coexistence Connector for Exchange

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

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.

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

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

• Reset Fast Validation in the Database

• Upgrade Inventory Version

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

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

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

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.