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

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.

Introduction

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

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.3.0 Cumulative Patch Set.

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

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

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:

Ensure Sufficient Hard Drive Space Before Patching

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

Search Service Refactoring Requires Additional Configuration

The Oracle Beehive 2.0.1.3.0 Cumulative Patch Set includes a refactoring of the Oracle Beehive Search Service (which was added in 2.0.1.2.1). This is a substantial change which may require additional post-configuration steps:

When patching Oracle Beehive Release 2 (2.0.1.2.0) or earlier:

The existing search index is erased during patching. As a result, after the upgrade any search operation on existing data will return no results. 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.

When patching Oracle Beehive Release 2 (2.0.1.2.1):

The existing search indexing process is suspended during patching. If you use a Zero Downtime Upgrade (ZDU) patching method, changes to searchable objects will not be indexed during the patching process. You can perform post-installation steps to update your existing search index with these accumulated changes.

If you do not use the ZDU method (that is, you elect to shut down your Oracle Beehive deployment during patching), then you do not need to perform any additional configurations steps. Your search index will not be affected by the patch.

Change Notification Service Removed from Coexistence Deployments

The Oracle Beehive 2.0.1.3.0 Cumulative Patch Set removes the Change Notification Service (CNS) component and integrates the functions it formerly performed directly within the Coexistence Connector. This change significantly reduces the complexity of the deployment and the disadvantages of deploying additional coexistence software on existing Microsoft Exchange servers.

After you apply the 2.0.1.3.0 Patch Set to all of your Oracle Beehive Coexistence Connector Oracle homes AND Oracle Beehive Coexistence Change Notification Oracle homes, you can remove CNS components by following the instructions in Remove CNS Components from Coexistence Deployments.

Installation Requirements

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

Oracle Beehive 2.0.1.3.0 Cumulative Patch Set can only be installed on Oracle Beehive Release 2 (2.0.1.0.0, 2.0.1.1.0, 2.0.1.2.0, and 2.0.1.2.1). 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.3.0 Cumulative Patch Set, Oracle strongly recommends that you perform a backup of your database and the Oracle Beehive Oracle home.

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

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

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

Disable Fast Validation in the Database

You must disable fast validation in the database before installing Oracle Beehive 2.0.1.3.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.3.0 Cumulative Patch Set, you can re-enable fast validation using the following commands:

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

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

To install 2.0.1.3.0 Cumulative Patch Set for Oracle Beehive Release 2 (2.0.1.0.0, 2.0.1.1.0, 2.0.1.2.0, and 2.0.1.2.1), perform the following steps on each Oracle Beehive server and Oracle Beekeeper Oracle home in your deployment:

Make sure that the Oracle Beehive Database instance and TNS Listener are UP and running.

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

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

Note:

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

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

Note:

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

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

Unzip the downloaded package to a convenient location.

For Oracle Beekeeper instances that were previously upgraded from 1.5.1.x to 2.0.1.0, work around a known issue (Bug 9041410) by performing the following steps to extract a custom script:

In the Oracle Beekeeper Oracle home, navigate to the patch storage directory:

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

Notes:

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

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

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

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

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

On UNIX and Linux:

% $ORACLE_HOME/OPatch/opatch napply

On Windows:

patch.bat napply

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

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:

On Linux x86, x86-64, and Oracle Solaris on SPARC (64-bit), download and install the patch for Bug 8481520.

On Windows or other operating systems, contact Oracle Support for the necessary patch.

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:

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.3.0 Cumulative Patch Set, you can re-enable fast validation using the following commands:

Run SQL Script uds_post_upgrade_seed.sql

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

BEEHIVE_HOME/beehive/tmp/patch/9553017

Upgrade Inventory Version

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

Navigate to the upgrade inventory script in the following location:

<extracted_patch_location>/9553017/custom/scripts

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:

BeehiveVersionUpgradeTo20130.zip

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

BeekeeperVersionUpgradeTo20130.zip

A subdirectory will be created containing the script

Run the shell script as follows:

In Oracle Beehive instances:

For Linux and UNIX:
% BeehiveVersionUpgradeTo20130.sh <PATH_TO_ORACLE_HOME>
or for Windows:
% BeehiveVersionUpgradeTo20130.bat <PATH_TO_ORACLE_HOME>

In Oracle Beehive DMZ and Coexistence Connector instances:

For UNIX and Linux:
% BeehiveVersionUpgradeTo20130.sh <PATH_TO_ORACLE_HOME>
or for Windows:
% BeehiveVersionUpgradeTo20130_DMZ_COEX.bat <PATH_TO_ORACLE_HOME>

In Oracle Beekeeper instances:

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

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

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

Start Oracle Universal Installer by invoking the runInstaller in this directory:

% ./runInstaller
or, on Windows:
% setup.exe

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

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.3.0 or Oracle Beekeeper 2.0.1.3.0

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

Search Service Post-Installation Configuration

The Oracle Beehive 2.0.1.3.0 Cumulative 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

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

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

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

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

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

To minimize performance impact, consider the following strategies:

Run the recovery crawler command during off-peak hours

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

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

Configuring Oracle Secure Enterprise Search (SES) Integration

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

Remove CNS Components from Coexistence Deployments

The Oracle Beehive 2.0.1.3.0 Cumulative 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 or 2.0.1.3.0 Cumulative 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:

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.

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

Migrate Data from DENY_ALL Groups to Folders With Private Sensitivity

To provide improved security, with this patch Oracle Beehive has implemented a new access control scheme for restricting access to content at the folder level. Instead of using the DENY_ALL permission on UDS groups, you can now use the 'private' sensitivity directly on a folder. To migrate from the previous method to the new method, workspace owners must re-create affected folders.

To facilitate this process, a SQL script is provided which creates a list of all folders with the DENY_ALL group permission. After installing this patch set, you can find the script at the following location on any patched Oracle Beehive server:

$ORACLE_HOME/beehive/db/accesscontrol/src/sql/upgrades/9761524.sql

Oracle recommends performing the following steps after installing this patch, to implement the improved security model:

Using SQL+Plus, Connect to the current Beehive CODE schema

Note:

To get the current code schema name, use the command beectl list_schemas.

Run the provided SQL script 9761524.sql. The output lists all folders with access denied to a group. An example of typical output is shown in Example 1, below.

Notify workspace owners (listed in the output loginid and contact fields) of the folder-group combination (listed in the folderpath and groupname fields) for which Oracle recommends using the new OBEO and OBEE feature of using sensitivity to control access.

Workspace owners must re-create the affected folders using OBEO or OBEE, assign the 'private' sensitivity-only sensitivity to each folder, and then move content from the old folders to the new ones. The old folders can then be removed.

You can write a script to generate e-mails based on this report and send collated e-mail messages to workspace owners. For example, one e-mail can be sent to rsmith@example.com indicating that the Analysts and EXECS workspaces have INBOX folders that should be re-created and assigned the 'private' sensitivity.

Resolved Issues

The issues that were resolved by the Oracle Beehive 2.0.1.1.0, 2.0.1.2.0, and 2.0.1.2.1 patch sets (and are included in this cumulative patch) are listed in detail in the patch readmes for each patch. You can find the readmes on the Oracle Technology Network Website, at the following URLs:

In OBEO, when multiple localized versions of a user's name are available, the language preference stored in Outlook will take precedence for local display of user's name(s).

7332250, 9703953, 9824559

When OBEO users send e-mail from a delegator's address, they can now choose for the From field to show "On behalf of" the delegator. By default, delegatees will be prompted when sending; the prompt includes a 'remember' setting, and users can control the dialog and settings using the delegates settings page of their personal workspace.

8214575

In OBEO, users can now display the full headers of a message by clicking View, and then selecting Message Source as MIME.

8260507

Support for migrating workspace data between deployments was added.

8746709

Workspace quota e-mail messages were using a non-configurable generic placeholder domain (example.com) for the From: address.

8892397

In Beekeeper, when configuring the Email Service, the behavior of expand/collapse buttons in the pop-up configuration windows was inconsistent.

9043173

In an e-mail portlet, clicking to view the profile of a selected user opened the acting user's profile instead.

9171248, 9699456, 9699464

OBEO users can now send follow-up flags and categories to e-mail recipients.

9187398

In an e-mail portlet, an error message was displayed when a user attempted to select the 'test tag' filter.

9194102

In Voicemail, the auto-attendant disconnected calls after the caller entered a user extension (correctly or not).

9199534

In the recent activity portlet, the View filters 'Tags', 'Tasks', 'Discussions', and 'Workspace Management' did not work.

9238086

In Oracle Webmail, approvals of workflow tasks initiated by another user failed without completing the workflow.

The beectl command export_email_data produced an error whenever an e-mail message content-type value was not set.

9401079

Due to shared port ranges across OC4J containers, the Email Service sometimes produced exception errors. Shared port ranges will now be subdivided across OC4J containers.

9405319

A performance improvement was made in the Time Management Service.

9440827

An issue caused slow UDS LDAP synchronization for users with a large number of direct reports.

9463961

In the Conferencing client for Mac OS X, after a conference with a large number of attendees, if the organizer ended the conference an attendee's client sometimes became unresponsive.

9475323

Voicemail messages were sometimes not delivered as attachments to a user's e-mail Inbox.

9477645

In the RIM Blackberry mobile client, e-mail messages did not include the Reply-to: header, and responses were sent to the Sender instead.

9483366

In Time Management, adding an attendee or resource to a recurring event where it was already a participant in at least one instance of that event caused an error, and the attendee was not added to any instances.

9483517

A rare exception that could be raised when sending an e-mail was fixed.

9486337

In Oracle Beekeeper E-mail configuration, an enable/disable function has been added to VMS sender and recipient matchers.

9502565

In Team Collaboration client Wikis with French locale (fr_FR), the Recent Activity and Search filter lists did not display single-quote (') marks or any characters after them.

9503055

When uploading files using the Team Collaboration client, cancelling the upload caused an inappropriate error message.

9528117

In a Team Collaboration client Wiki page, putting a question mark (?) into a heading that is included in a table of contents caused the table of contents link to break.

9532396

A performance issue in the Voicemail Service was identified and fixed.

9537737

After changing a user's working hours in Beehive Central, that user's non-working time was incorrectly shown as free.

9545218

When uploading files using the Team Collaboration client, the entire file path was shown for files selected for upload, which usually obscured the actual file name. File names are now also shown seperately.

9545274

A persistent 'ORA-1403' error that could occur in the Time Management Service was identified and fixed.

The Mobile Device Management Service could not synchronize with HTC Ozone XV6175 devices.

9554373, 9824379, 9841024

A number of performance enhancements were implemented.

9556353

URLs pasted into a Team Collaboration client Wiki page 'Add external link' dialog box were not recognized as links.

9557971

Some instant messages were not received when a user logged in to multiple sessions.

9562747

In Firefox 3.0.x, uploading files to the Team Collaboration client froze on the "Upload Files" dialog box.

9563165

In the Team Collaboration client Announcements page, the Overview button was not clickable.

9571317

CalDAV scheduling with iPhone OS 4.0 is now supported.

9571756

Mozilla Firefox 3.6.x is now supported.

9572761

In Apple iCal 4.0.2, trying to accept an invitation to a recurring event with one or more canceled recurrence instances, or specifing a recurrence rule with the WKST (week start) rule part, returned a 400 Bad Request error.

9576283

A number of improvements and issues were identified in IMIP integration with Microsoft Exchange.

9580486

In the Team Collaboration client Wiki pages, tables inserted in Edit mode did not have visible grid lines.

9580933

In the Team Collaboration client Wiki pages, bulleted lists inside tables on pages that were originally created in a 1.5.x version of Oracle Beehive were no longer displayed.

9581333

E-mail meeting invitations were not sent to external contacts that did not have a timezone set.

9581817

Oracle Beekeeper does not support Mozilla Firefox 3.6; an "Unsupported browser" message will now be shown.

9588428

In the Team Collaboration client Wiki pages, table cells set to word wrap in Edit mode, did not word wrap once displayed.

9637465

E-mailed contacts were repeatedly synchronized to mobile devices by the Mobile Data Sync Service, creating multiple contacts on the device.

9644713

Workspace names containing a Tab character were displayed without any whitespace on the Overview page, or when searching for the workspace.

9644889

In the Team Collaboration client Wiki interface, when a user entered some text and then selected a suggested wiki page, the entered link text did not update to synchronize to the selected page.

9654241

In standards-based calendar clients, a MODIFICATION_FAILED error was returned when changing the title of a meeting with a primary default reminder.

On the Mobile Blackberry client, attempting to modify a task produced an error.

9656921

On French (fr_FR) locales, the Change Rule button in the Team Collaboration client was displayed incorrectly.

9663430

In OBEO, an upload error was generated when a team workspace participant without write access opened a contact in the team workspace Contacts folder.

9665336

On deployments using Oracle Database 11.1.0.7.2, the Email Service could only delete 100 messages during each purge command, resulting in undeleted messages consuming excessive storage quota.

9668928

In OBEO, when making a free/busy lookup, a long e-mail address could somtimes cause Outlook to crash.

9669314

When a message was sent to multiple users, a problem with one user account triggering a retry could cause the message to be repeatedly sent to all of the other users as well.

9673040

Users can now disable delivery of meeting and task requests to their OBEO Inbox from a Workspace's Advanced Settings page.

9673398

When users connect to Oracle Beehive from OBEO, if they have an out-of-office notification currently set, they will now receive a pop-up dialog box with options allowing them to disable the notification or open the notification settings.

9675866

In the Team Collaboration client Wiki markup help, the infobox tag was misspelled.

9678537

In the Team Collaboration client calendar, when a recurring event had instances spanning from one month into the next month, only the first instance of the meeting was shown in the calendar.

9684626

In the Team Collaboration client Wiki dialog for inserting/editing links, there were display issues when the target folder contained hundreds of files.

On SSL-enabled Oracle Behive instances, Team Collaboration client Wiki links in the Comments section to documents from other workspaces used the non-SSL 'http:' protocol, causing these links to fail.

9692381

In OBEO, when a user had been delegated full manage privileges by another user, their archiving settings archived and removed content from the delagator's calendar.

By default, only private folders will now be set to 'Archive items using default settings'. All the other folders default to 'Do not archive items in this folder,' although users can still manually change this setting on their folders.

9693239, 9693362, 9693422, 9693450 9693298

Internet Explorer 8 is now a certified and supported browser for the Team Collaboration client.

9693277

When a delegatee replied or forwarded an e-mail on behalf of a delegator, that e-mail was sometimes not copied to any user's Sent Items folder.

9694490

When a mobile device user edited and then saved a calendar event without making actual changes, Beehive still triggered workflows, meeting change notifications, and send update e-mails to coexisting users as if the event had been changed.

9695733

There was a problem with relaying e-mails that matched a NonLocalEmailPattern that was a modified version of a LocalEmailPattern in the form <local_email_pattern>.<additional_domain>

9703803

The Time Management Service's logging entries were improved.

9712110

In OBEO and OBEE, automatic DMS-based client updates can be disabled by setting the following key in the beehive.ini file:

[Default
DISABLE-AUTOMATIC-DMS=TRUE]

When this setting is enabled, the 'Check for update' button on the client is disabled, and the client will not download DMS-based updates.

9716926

Users sometimes received multiple ASK Service notifications for the same event.

9734068

There were some minor display issues in the Team Collaboration client Announcements page.

9735687

Improvements were made to the process of converting Coexisting Resource Users (CRUs) to Coexisting Beehive Users (CBUs).

9736332

In the Team Collaboration client Wiki page table of contents, long section titles did not wrap correctly.

9738616

After upgrading from 1.5.x to 2.0.1.2, Oracle Beekeeper could not communicate with the server in SSL mode. To fix the issue, a new property for the wallet password must be configured for the the Beekeeper UnmanagedOC4J component

9748898

Changes in a new time zone package, Olson time zone package 2010J, were applied.

9749053

A problem causing out-of-memory crashes in IBM Domino coexistence when processing data imports was fixed. Additionally, a new property has been added that suspends data import processing:

After routing e-mails through the Coexistence Connector, IBM Domino processing stripped some header information before sending them to Coexisting Beehive Users; this caused iMIP messages to appear in text-only format.

9756472

In the Team Collaboration client, search results containing very long workspace names had overlapping text.

9760124

In the Conferencing client, if a user had an invitation to a conference where the organizer's account was no longer in Beehive, error messages prevented display of any current and upcoming conferences.

In Oracle Beehive 2.0.1.2.1, users who perform a search of e-mail using a standards-based client (such as Mozilla Thunderbird) received inappropriate results, or did not receive certain results, when using compound search terms.

9782162

Under rare circumstances, canceled workspace folder move operations using OBEO or OBEE could delete the workspace.

9782744

Documentation for using Instant Messaging and Presence in the RESTful Web Services SDK was missing.

9785628

A synchronization error with the Mobile Blackberry client could cause an error message when attempting to synchronize a change very soon after a previous sync.

9787942

In the Team Collaboration client Wiki pages, while posting a comment, cancelling caused the Publish and Cancel buttons to disappear

9788552

When Beehive was configured with user accounts mastered in an LDAP-based directory, custom Beehive user attributes not in the LDAP directory could not be updated in Beekeeper.

9792172

A performance enhancement was made to the Search service.

9795577

Search results beyond the first ten were not shown in the abbreviated format beyond the first page of results.

9798707

A performance issue in the Search Service was identified and fixed.

9800153

In OBEO, an e-mail sender's display name containing non-ASCII characters included in the From: field was not properly encoded, which could cause display issues for some recipients.

9801349

A performance issue with presence lookup in the Time Management Service was identified and fixed.

9802762

The search service index recovery crawler was not indexing meetings when the description was in a certain size range.

9810305

In the Beehive Development Kit, calendar free/busy lookup wasn't working.

9815962

In large deployments, high levels of workspace folder and document activity caused recent activity tracking to degrade server performance. A new Workspace Service property, RecentActivityInPersonalWorkspaceEnabled, now controls whether recent activity should or should not be tracked for personal workspaces. The default value is False. Set the property to True to enable recent activity tracking.

9819206

Oracle Beekeeper did not show dynamic group details when the group was based on a custom property.

9820438

Meeting invitations in the Trash are no longer indexed by the Search Service.

9823458

In [pt-BR] (Brazilian Portugese) and [fr-CA] (French Canadian) localized versions of Oracle Webmail, the sent items folder displayed the From: field instead of the To: field.

9825797

An issue could intermittently prevent users from joining a Web conference.

9828422

After setting a user's presence to 'DND' automatically due to an active meeting to which the user was invited, if the user then declined the meeting, the presence was not correctly reset.

9828677

In Oracle Webmail, attempting to retrieve an e-mail from a deleted and purged user produced a SOAP sender error.

9829492

The Mobile Device Management Service now supports the Apple iPad.

9832231

Performance in the Search Service e-mail change capture indexing was improved.

9839334

Windows 7 WebFolders is now a certified and supported client for the Beehive WebDAV server.

8260507

Introduced beectl export_workspace and import_workspace commands to archive or load a workspace, its members and settings, and the most recent version of wiki pages and documents within it.

9839522

Users will no longer re-download their entire calendar after an Oracle Beehive server upgrade.

9845055

An exception was occuring when the Mobile Data Sync Service connected to RIM Blackberry devices on Blackberry OS 4.2.

9846084

A performance improvment was made to initial loading times for the Team Collaboration client.

9846703

In Oracle Webmail, pasting content containing a blank line into the description editing field in HTML mode prevented the description from being saved.

9854444

An intermittent error in the Web Conferencing service could cause some conference rooms to become un-joinable.

Globalization Issues

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

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.