Skip Headers

Oracle® Beehive 2.0.1.2.1 Patch Set Readme
For Oracle Beehive Release 2 (2.0.1.2.0) (All Platforms)
 

 

Oracle® Beehive

2.0.1.2.1 Patch Set Readme

For Oracle Beehive Release 2 (2.0.1.2.0) (All Platforms)

June 2010

Readme updated June 25, 2010

This Readme accompanies 2.0.1.2.1 Patch Set for Oracle Beehive Release 2 (2.0.1.2.0).

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

If you have not already upgraded your deployment to Release 2 (2.0.1.2.0), you may be able to upgrade your Oracle Beehive installation to that version 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.

Once you have completed an upgrade according to one of these paths, you can then apply this 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:

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.1 Patch Set for Oracle Beehive Release 2 (2.0.1.2.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:

Must Install Oracle Beekeeper Prior to Applying Patch

If you have not already installed an instance of Oracle Beekeeper, but you think you might want to use Oracle Beekeeper in the future, you must install Oracle Beekeeper before installing the 2.0.1.2.1 Patch Set.

Once you install the 2.0.1.2.1 Patch Set, you cannot install a new instance of Oracle Beekeeper.

Oracle Beekeeper must be patched to 2.0.1.2.1 to work with Oracle Beehive 2.0.1.2.1. Earlier versions of Oracle Beekeeper will not work with Oracle Beehive instances that have been patched to 2.0.1.2.1.

Installation with Oracle Enterprise Manager Not Supported

Applying 2.0.1.2.1 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.

Search Service Refactoring Requires Additional Configuration

The Oracle Beehive 2.0.1.2.1 Patch Set includes a refactoring of the Oracle Beehive Search Service. 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.

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

Oracle Beehive 2.0.1.2.1 Patch Set can only be installed on Oracle Beehive Release 2 (2.0.1.2.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.1 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.

Disable Fast Validation in the Database

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

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


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.

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.1 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>/9699389/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:

      BeehiveVersionUpgradeTo20121_linux.zip
      BeehiveVersionUpgradeTo20121_sol.zip
      BeehiveVersionUpgradeTo20121_win.zip
      
    • In Oracle Beekeeper instances, extract the files from the following .zip for your operating system:

      BeekeeperVersionUpgradeTo20121_linux.zip
      BeekeeperVersionUpgradeTo20121_sol.zip
      BeekeeperVersionUpgradeTo20121_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:
      % BeehiveVersionUpgradeTo20121.sh  
                                                  
      <PATH_TO_ORACLE_HOME>
      or for Windows:
      % BeehiveVersionUpgradeTo20121.bat  
                                                  
      <PATH_TO_ORACLE_HOME>
                                                
    • In Oracle Beehive DMZ and Coexistence Connector instances:

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

      For UNIX and Linux:
      % BeekeeperVersionUpgradeTo20121.sh  
                                                  
      <PATH_TO_ORACLE_HOME>
      or for Windows:
      % BeekeeperVersionUpgradeTo20121.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.1

  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.1 or Oracle Beekeeper 2.0.1.2.1

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

      On Windows, also confirm:

      Oracle Collaboration Coexistence Gateway 2.0.1.2.1
      

      On Oracle Beekeeper:

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

Search Service Post-Installation Configuration

The Oracle Beehive 2.0.1.2.1 Patch Set includes 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

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 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 entitie types. You can specify this option more than once to indicate mulitple 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

Configuring Oracle Secure Enterprise Search (SES) Integration

If you are using Oracle Secure Enterprise Search (SES) with Oracle Beehive, 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

Remove CNS Components from Coexistence Deployments

The Oracle Beehive 2.0.1.2.1 Patch Set removes the Change Notification Service (CNS) component and integrates the functions it formerly performed directly with the Coexistence Connector.

At any time after installing 2.0.1.2.1 Patch Set on all of your Oracle Beehive Coexistence Connector Oracle homes AND Oracle Beehive Coexistence Change Notification Oracle homes, you can perform the following steps to remove CNS components:

  1. Patch ALL Oracle Beehive Coexistence Connector Oracle homes and Change Notification Service Oracle homes. You must not remove CNS components until every Coexistence Oracle home has been patched.

  2. From CNS (or Connector+CNS) Oracle homes, run the following command to clean up CNS registrations:

    $ORACLE_HOME\beehive\collabcoex_connector\coexctl.exe remove_cns_registrations
    
  3. Uninstall CNS-only Oracle homes using Oracle Universal Installer.

Resolved Issues

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

Table 2 Resolved Issues in Oracle Beehive 2.0.1.2.1 Patch Set

Bug Number Description

9266572

In OBEO, multi-byte characters in multipart/alternative e-mails appeared garbled if the HTML alternative part had no character set defined in the MIME source, but the text alternative part had the correct charset set defined.

9440827

Performance of UDS updates was slow when an affected user account's manager had a large number of direct reports.

9451105, 9677380, 9703543

OBEO now supports sending and responding to IMIP-style meeting invitations and responses, including to external users.

9472193

To improve message submission times during adverse conditions, OBEO now uses an adaptive retry interval when attempting to send messages to the server.

9491474

In deployments synchronizing with an LDAP-based user directory, user accounts whose e-mail addresses were only mapped to a 'proxy' address type could not be included in the Oracle Beehive Webmail global address list.

9500467

The output of the beectl command list_coexistence_profiles --file <filename> could include accented characters in user names which were not valid for UTF-8 encoding, rendering the file unparsable for the modify_coexistence_profiles command.

9719715, 9506066

In OBEO, no attachment marker was displayed when an e-mail contained an inline attachment.

9523733

In OBEO, copying an e-mail from the Inbox to any other folder while the Reading Pane is ON caused the Received Date of the copied email to be altered.

9542336, 9596399, 9699438, 9708616, 9751392, 9757786, 9761122, 9768926, 9769324

The Oracle Beehive Search sevice has been refactored. See Search Service Refactoring Requires Additional Configuration and Search Service Post-Installation Configuration.

9572145, 9572333

Oracle Beehive Coexistence installations no longer need a Change Notification Service. See Change Notification Service Removed from Coexistence Deployments and Remove CNS Components from Coexistence Deployments

9657321, 9669116

In OBEE, the warning message displayed when a user attempts to delete workspaces has been improved

9672875

The third-party application Cisco WebEx crashed after it sent messages to OBEO for delivery while Microsoft Outlook was not running.

9677080

In Beehive Webmail, using the time zone for "(GMT-04:00) Georgetown, La Paz, Manaos, San Juan" caused all event times to be shown 30 minutes later than they should.

9677958

A problem caused synchronizations with the Mobile Data Sync Server to fail.

9682997

In a coexistence environment, users who were converted from CRU to CBU by default received e-mail meeting reminders 10 minutes after the meeting start time, instead of 10 minutes before.

9698921

On multi-CPU Solaris deployments, an error in the Mobile Data Sync Service caused it to over-count the number of active concurrent sessions, eventually preventing new sessions even though the limit was not actually reached.

9788518

The large server deployment template now places Time Management services in the BEEINTEGRATION component, and heap sizes were adjusted to accomodate the changes.

9735122

Previously, when managing permissions for users or groups for any given folder in a workspace, setting the Permission Level for 'anyone' to 'Deny All' did not deny users that were members of the workspace from viewing the Folder or its contents. It was necessary to specifically select users and 'Deny All' for those users to no longer have access to the folder and its contents.

The 'deny all' setting is no longer available for groups within workspaces. Now, a folder in a team workspace can be hidden from all members of a team workspace by setting the default sensitivity of that folder to be Private, and granting explicit access only to those users that should have access.


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.


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

Left Curve
Popular Downloads
Right Curve
Untitled Document
Left Curve
More Middleware Downloads
Right Curve