Oracle® Beehive

Installation

To install 2.0.1.2.1 Patch Set for Oracle Beehive Release 2 (2.0.1.2.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 9699389
   

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.2.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 apply -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: %ORACLE_HOME%\OPatch\opatch apply -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 apply -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: %ORACLE_HOME%\OPatch\opatch apply -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:

     
     

     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 apply
     

     On Windows:

     %ORACLE_HOME%\OPatch\opatch apply
     

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

     On Windows:

     %ORACLE_HOME%\OPatch\opatch apply
     

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

     %ORACLE_HOME%\OPatch\opatch apply -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.

Globalization Issues

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