Middleware
Beehive
Overview
| Oracle® Beehive 2.0.1.1.0 Patch Set Readme For Oracle Beehive Release 2 (2.0.1.0.0) (All Platforms) |
2.0.1.1.0 Patch Set Readme
For Oracle Beehive Release 2 (2.0.1.0.0) (All Platforms)
March 2010
Readme updated May 10, 2010
This Readme accompanies 2.0.1.1.0 Patch Set for Oracle Beehive Release 2 (2.0.1.0.0).
This option installs 2.0.1.1.0 Patch Set, for installations of Oracle Beehive Release 2 (2.0.1.0.0) only. Before applying this patch, you must upgrade your Oracle Beehive Release 1 deployment to Release 2 (2.0.1.0.0). Do not attempt to install this patch set on earlier versions of Oracle Beehive.
This Readme contains the following topics:
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.
This Readme includes information on how to install 2.0.1.1.0 Patch Set for Oracle Beehive Release 2 (2.0.1.0.0).
Oracle recommends that you read and understand the information in this document before beginning the installation.
Please review the following important notes before installing this patch:
Applying 2.0.1.1.0 Patch Set using Oracle Enterprise Manager is 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.
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:
Bug 9530414. Due to a problem with the Windows version of Oracle Beekeeper patch set installation, the patch set may appear to freeze or hang after completion without exiting. If you see the message "Beehive Upgrade completed," but the patch set does not subsequently exit, open a new command shell in the Oracle Beekeeper Oracle home, and run the following command:
opmnctl stopall
This will end the patch set installer process.
2.0.1.1.0 Patch Set adds a new property to the EmailService:CSIProperties component. The new VMSProperties property stores the name of a virtual mail server (VMS) (by default, the OutboundVMS). Oracle Beehive will apply the limits on message size and recipient count stored as part of that VMS, to all Beehive-internal (CSI) e-mail messages sent from Oracle Beehive clients, such as Oracle Beehive Webmail and OBEE.
This allows you to configure maximum message size and maximum recipient count for your entire Oracle Beehive deployment in one place (the OutboundVMS), and those limits will apply to all e-mail traffic.
You must conform to each of the following requirements and perform all pre-installation tasks before installing the patch:
Caution: Failure to carefully read and understand these requirements may cause Oracle Beehive to malfunction, including interruption of service, loss of data, or both. |
Install on Oracle Beehive Release 2 (2.0.1.0.0) Only
Oracle Beehive 2.0.1.1.0 Patch Set can only be installed on Oracle Beehive Release 2 (2.0.1.0.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.1.0 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 Patch 8440319
You must install a database patch before installing 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.1.0 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.1.0 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.1.0 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:
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. |
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") )
Restart the database listener and the database
Notes:
|
To install 2.0.1.1.0 Patch Set for Oracle Beehive Release 2 (2.0.1.0.0), 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.
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.
Unzip the downloaded package to a convenient location.
Set your current directory to the directory where the patch is located. For example:
% cd 8998918
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
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:
|
% 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.1.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, run the following commands:
% cd $ORACLE_HOME/.patch_storage % unzip <patch_extract_location>/8998918/Beehive_2011/9041410_workaround.zip
After extracting the file to your Oracle Beekeeper instance, you can proceed with the 2.0.1.1.0 upgrade:
Notes:
|
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:
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
Be sure to repeat all steps in this procedure on each Oracle Beehive server in your deployment.
After performing the installation, perform the steps in the following sections, where applicable:
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 thehasbind 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. |
After you install the Oracle Beehive 2.0.1.1.0 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='*';
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>/8998918/Beehive_2011/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 for your operating system:
Beehive_2011/custom/scripts/BeehiveVersionUpgradeTo20110_linux.zip Beehive_2011/custom/scripts/BeehiveVersionUpgradeTo20110_sol.zip Beehive_2011\custom\scripts\BeehiveVersionUpgradeTo20110_win.zip
In Oracle Beekeeper instances, extract the files from the following .zip for your operating system:
Beehive_2011/custom/scripts/BeekeeperVersionUpgradeTo20110_linux.zip Beehive_2011/custom/scripts/BeekeeperVersionUpgradeTo20110_sol.zip Beehive_2011\custom\scripts\BeekeeperVersionUpgradeTo20110_win.zip
A subdirectory will be created containing the script
Run the shell script as follows:
In Oracle Beehive instances:
For Linux and UNIX: % BeehiveVersionUpgradeTo20110.sh <PATH_TO_ORACLE_HOME> or for Windows: % BeehiveVersionUpgradeTo20110.bat <PATH_TO_ORACLE_HOME>
In Oracle Beehive DMZ and Coexistence Connector instances:
For UNIX and Linux: % BeehiveVersionUpgradeTo20110.sh <PATH_TO_ORACLE_HOME> or for Windows: % BeehiveVersionUpgradeTo20110_DMZ_COEX.bat <PATH_TO_ORACLE_HOME>
In Oracle Beekeeper instances:
For UNIX and Linux: % BeekeeperVersionUpgradeTo20110.sh <PATH_TO_ORACLE_HOME> or for Windows: % BeekeeperVersionUpgradeTo20110.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.1.0
To verify that the inventory on an instance has been updated, perform the following steps:
Navigate to the following directory:
% cd <Updated_Beekeeper_ORACLE_HOME>/oui/bin or % cd <Upgraded_Beehive_ORACLE_HOME>/oui/bin
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.1.0 or Oracle Beekeeper 2.0.1.1.0
To confirm the versions of other subcomponents, expand Oracle Beehive or Oracle Beekeeper 2.0.1.1.0 by clicking on the plus (+) just before it. Traverse through the list of subcomponents and confirm the following upgraded components:
On Oracle Beehive:
Oracle Beehive Release 2 Configuration 2.0.1.1.0 Oracle Beehive Release 2 Database Support 2.0.1.1.0 Oracle Beehive Release 2 Binaries 2.0.1.1.0 Oracle Beehive Release 2 Libraries 2.0.1.1.0 Oracle Beehive Release 2 Services 2.0.1.1.0 Oracle Beehive Release 2 Configuration Wizard 2.0.1.1.0 Oracle Commuication and Messaging Services 2.0.1.1.0 Oracle Beehive Release 2 Oneoffs 2.0.1.1.0
On Windows, also confirm:
Oracle Collaboration Coexistence Gateway 2.0.1.1.0
On Oracle Beekeeper:
Oracle Beekeeper 2.0.1.1.0 Oracle Beekeeper OC4J 2.0.1.1.0 Oracle Beehive Release 2 Oneoffs 2.0.1.1.0 Oracle Beehive Release 2 Configuration Wizard 2.0.1.1.0
Table 1, "Resolved Issues in Oracle Beehive 2.0.1.1.0 Patch Set" lists the issues resolved in this Patch Set (new for 2.0.1.1.0 Patch Set).
Table 1 Resolved Issues in Oracle Beehive 2.0.1.1.0 Patch Set
| Bug Number | Description |
|---|---|
7614078 | In the Oracle Web Conferencing component, starting or restarting an MX during high-load situations could cause the OWC OC4J container to crash. |
7650398 | In Oracle Beehive Webmail, parts of Oracle Beehive-generated delivery status notification e-mails were not displayed. |
8316294 | In OBEO, the list of default sensitivities shown in the selection box when settting sensitivity is now sorted in order from most-permissive to least-permissive. |
8663429 | In Oracle Beehive Webmail, when creating an event and searching for resources, the Location, Contact and Room Capacity information is now displayed in the search results. |
8681444 | An issue with viewing .txt document versions in OBEE was identified and fixed. |
8720525 | Users could not join online conferences linked from an event in a calendar portlet. |
8737998 | Updates to the visibility (privacy) of events made in some standards-based calendar clients were not always visible in other clients. |
8772889 | Improvments were made in the handling of timeout operations when delivering e-mail. |
8801909 | On Windows Vista installations of the conferencing client, connecting to an older version server initiated an installation update, which failed. |
8851013, 8851275 | E-mail messages containing multibyte (NLS), non-UTF-8 content in the header fields, and sent to OBEO addresses, showed garbled header text to the recipient. |
8917177 | Certain document types, when opened from a workspace folder in OBEE, were always versioned immediately even though the user had not made any changes yet. Workspaces will now wait for 3 seconds before attempting to process updates to a document; if changes are made during that time, the checksum is updated and no new version is created. |
8993436 | During initial setup after installing OBEE, switching to Visible Workspace view and then back to Available Workspace view caused the workspace names to be duplicated in the list. |
8994066 | In OBEE, a personal workspace exported to a .pst file only exported the Inbox. |
9021342 | In the Conferencing client, connecting to a Device Management server failed when using auto-proxy detection, Microsoft Windows Internet options configured with a specific proxy, and a server instance is only accessible through that specific proxy. |
9027610 | Some localized (translated) versions of new and updated meeting invitation notifications contained errors. |
9028272 | To allow limits to be set on internal e-mail traffic (from and to Oracle Beehive users using Oracle Beehive native clients such as OBEO and Webmail), the EmailService:CSIProperties sub-component has a new property: |
9029326 | After migrating tasks to Oracle Beehive from Oracle Collaboration Suite, certain time zone differences in task start or completion times were not calculated correctly in Oracle Webmail. |
9059548 | A problem with search results when searching for certain document types was identified and fixed. |
9100975 | URLs embedded in meeting invitation notifications sent to RIM BlackBerry devices were sometimes malformed. |
9120082 | Improvements were made in the "sort by relevancy" function when searching for content in the Workspaces client. |
9124120 | In OBEO, sent meeting invitations and notifications will now be copied to the Sent Items folder. |
9134110 | In OBEO, if a user invites an Oracle Beehive user to an event using their SMTP e-mail address, Oracle Beehive will now attempt to match that address and supply free/busy data back to OBEO. |
9140960 | User preferred locales for Voicemail that included a hyphen (-) character, such as zh-tw or zh-cn, were not taking effect. |
9149690 | When using the "ASK Service" interface for actionable notifications, the View Profile command sometimes failed. |
9153551 | In the Conferencing client, if a user had more than 20 upcoming and current events, some were not initially displayed in the conference list. |
9160931 | In OBEO, if a grantee attempted to modify a file set to |
9167410 | In the Apple OSX version of the Conferencing client, the pause and resume recording functions did not work correctly. They have been removed. Users can still use stop and start functions. |
9167912 | In OBEO, failure log entries for blocked message attachments with detected viruses now indicate the exact message and attachment. |
9171831 | OBEO will no longer freeze while attempting to look up free/busy information for attendees of events while in Offline mode. |
9175742 | In the Apple OSX version of the Conferencing client, recordings of conferences with titles more than 80 characters long were not saved. |
9175937 | In the Apple OSX version of the Conferencing client, recording buttons are no longer available to participants when the host begins recording the conference. |
9177357 | In Oracle Beehive Webmail calendar events, when changing the status of an occurrance of a recurring event in day view, tags on the event disappeared. |
9178543 | Searches performed at an organization level of scope returned results that included workspaces and folders outside the organization. |
9190328 | There was a problem with incorrect search results for folders. |
9190548 | HTC Whitestone XV 6975 devices could not register with Oracle Beehive. |
9190633 | The Search service now suports queries against e-mail, files, and calendar where no keywords are provided. |
9192694 | On some locales, updated meeting notifications were missing values for date and time. |
9193320 | A performance improvement in the Search service was made. |
9194956 | In the Apple OSX version of the Conferencing client, adjusting any volume settings while using an external USB microphone caused the client to set the microphone to mute. |
9195140 | In workspaces announcements, HTTPS URLs are now converted to links in the same manner as HTTP URLs. |
9195212 | In Oracle Beehive Voicemail, when an auto-attendant caller used the directory module defined for local facility lookup and the property isGlobalLookupFallbackEnabled was set to true, fallback to the global directory on unsuccessful local lookup did not work correctly. |
9199053 | The Search service now supports the use of exclusion terms using the minus sign. For example, the search terms "database -customer" returns results containing the word "database" which do not contain the word "customer". |
9199071 | The Attendees and Location fields of calendar events are now available for search queries. |
9201965 | The Workspaces client Wiki page Filter tab is too narrow for some localized versions to display the full text of various options. The filter options now have tooltip popup messages to provide complete text. |
9202206 | When a user creates a new event in a workspace using the Workspaces client, there is now a text label reminding that all members enrolled in the workspace calendar will receive an invitation to the event. |
9203010 | In Oracle Beehive Webmail, bookmarked automatically-populated contacts (such as manager, peer, and direct report) are now editable. |
9212492 | In the Windows Conferencing client, the pause and resume buttons are no longer available for invitees. |
9218109 | In the Workspaces client Wikis, non-ASCII characters included in HTML markup for a wiki page were displayed incorrectly. |
9219105 | In Oracle Beehive Webmail, users could not add or remove attachments from one instance of a recurring event. |
9223421 | A performance issue with resetting default access permissions when revoking delegate rights was identified and fixed. |
9227817 | In the Workspaces client on Internet Explorer, when accessing files not enabled for version control, users could click grayed-out check in and check out buttons. |
9233067 | An internal error prevented moving address book folders. |
9233700, 9233843, 9255794, 9402220, 9455522 | Several potential database deadlock issues were resolved. |
9241528 | Oracle Beehive Webmail now accepts e-mail addresses containing valid special characters, such as the apostrophe ('). |
9245478 | In Oracle Beehive Webmail, the Notes field for contacts was limited to 1000 characters. Users can now enter as much as 58Kb of data in the Notes field, which is the default Oracle Beehive limit. |
9246729 | After upgrading Oracle Beehive from 1.5.1.4.0 to a later version, messages addressed to a team workspace that existed prior to the upgrade were not sent to the workspace participants. |
9248605 | After delegating full calendar access to another user, the delegatee could not view custom contact ACEs in Oracle Beehive Webmail. |
9249089 | In Oracle Beehive Webmail calendar view, visible details for an event were limited by the length of the event subject field. The view will now be extended to show more text in other fields even if the event subject is short. |
9249736 | Exess logged error messages in Oracle Beehive internal search document indexing were corrected. |
9250778 | In OBEE, changing the location of the offline cache caused all files in the original location to be deleted. Now, only OBEE-related files will be removed. |
9254298 | A new feature, Pluggable Authentication Framework, has been added to Oracle Beehive. See "Integrating Third-Party Single Sign-On Providers with Oracle Beehive" in the Oracle Beehive Integration Guide for details. |
9255210 | In Oracle Beehive Webmail, after using the 'file as' feature for a contact and removing information such as company or last name, empty parentheses or commas were still displayed. |
9256332 | An improvement in Oracle Beehive federated search performance was made. |
9257267 | An out of memory condition in the BEECLIENT component could occur due to an inefficient cacheing scheme related to the Oracle Beehive Webmail client. |
9257944 | In the Workspaces client, entering an invalid value for the completion percentage of a task did not produce a warning or error message. |
9263747 | Oracle Beehive e-mail portlets displayed the Open Profile function for external users (which don't have profiles). |
9264398 | Performance improvements in the Oracle Beehive server related to high-availability deployments were identified and implemented. |
9265108 | The Workspaces client wiki editor allowed the user to input invalid dimensions when uploading an image for display on a wiki page. |
9265217 | On Internet Explorer, the Workspaces client did not display all different types of comments for a document or wiki page correctly on the comments tab. |
9270897 | On a Workspaces client wiki page in a workspace that had been renamed, links pointing to nonexistent pages failed to load the "create new page" dialog. |
9271777 | Oracle Webmail failed to load calendar information when a calendar portlet user viewing a non-recurring calendar event that was created in a team workspace clicked on the details URL. |
9273901 | Several minor display issues involving Workspaces client wiki pages in Microsoft Internet Explorer 8 were identified and resolved. |
9275696 | After coexisting remote Lotus Domino users modified personal recurring meetings with exceptions, changing the user to a coexisting Beehive user caused meetings to be re-imported with some failures, and also losing some of the modifications. |
9282639 | Notifications for coexisting remote users are now disabled. |
9283631 | E-mail messages originally moved to an outbox in Oracle Connector for Outlook, then archived, and then re-loaded into the outbox in OBEO (such as after an upgrade to OBEO), could not be sent and blocked the outbox. |
9286546 | By default, the HTML plugin for Workspaces client wiki pages is now disabled. Previously, this functionality was enabled by default. |
9289824 | Some performance issues with evaluating e-mail server-side rules using regular expressions were identified and fixed. |
9290947 | In the Beehive Conferencing client, while in 2-window mode, reconnecting to a conference could sometimes cause the client to crash. |
9292580 | Problems with downloading updates to the Oracle Beehive Conferencing client for Apple OSX could occur if the user had launched the application from a locked volume. The client now prevents launching the download manager from a locked volume. |
9292637 | OBEO did not work in Microsoft Outlook 2003 and 2007, on installations of Microsoft Windows Server 2003 and 2008, using Korean or French localized versions of those operating systems. |
9297325 | A problem with retrieving very large lists of serialized configuration data from the database (such as with a deployment with a large number of Application tiers) was identified and fixed. |
9298814 | In Oracle Beehive Webmail, delagatees could not open files attached to a task assigned from a delegator. |
9301526 | A new feature, incremental team workspace evolution, has been added to Oracle Beehive. See the Oracle Beehive Release Notes for details. |
9302202 | In OBEE on Windows 7, after resetting the favorite and visible workspaces, the Manage Workspaces dialog box sometimes re-loaded and the changes made were lost. |
9302511 | A potential deadlock condition with competing e-mail threads in the Email Service was identified and fixed. |
9302846 | When sending a message from a shared folder using Oracle Beehive Webmail, only the e-mail address was shown in the Sent By: and On Behalf Of: fields, even when a display name was available. |
9303047 | After performing an upgrade, the XMPP chatroom 'last modified' time was incorrectly updated with the upgrade timestamp. |
9305200 | In order to allow delegated calendar and tasklist sensitivities to be displayed properly to a delegatee in OBEO, an ACL is now set on the container that holds those sensitivities at the time delegated access is granted. |
9306258 | PDF formatted attachments to e-mail messages could not be opened from Oracle Beehive Webmail or OBEO clients. |
9309157 | In a Lotus Domino coexistence deployment with many Domino servers, a memory consumption problem caused the coexisting Domino server to crash. |
9310627 | If the startup folder when launching Microsoft Outlook was not within the OBEO folder heirarchy, various Oracle Beehive data and functions could not be accessed. |
9314536 | If an Oracle Beehive user was the owner of a team workspace but had an external calendar, the external calendar setting was ignored and the user could not schedule events with that calendar. |
9315614 | When accessing the Workspaces client, if the browser was set to a non-supported locale, the Apply button shown when creating a new workspace did not function. |
9315697 | Accepting a meeting invitation using actionable notifications failed when the response e-mail included various combinations of plain text, HTML, or having a signature or image attachment. |
9318101 | A problem with message sorting of very large lists of e-mails from Oracle Beehive Webmail clients caused excessive memory consumption on the server. |
9321966 | In Oracle Beekeeper, the label and hint for the new pattern field of pre-resolution domain rewriting rules were incorrect. |
9325542 | The wiki editor in the Workspaces client sometimes duplicated askterisk characters (*) entered in rich text mode. |
9329082 | Under certain conditions, using Beehive Central or beectl to grant access rights to confidential calendar events also granted access to private events. |
9329700 | The script schema_deinstall.pl incorrectly dropped the BEE_CDCPUB schema if only one schema was specified using the --schema_name option. |
9339755 | Performance, error-handling and logging improvements were made in the coexistence framework. |
9342375 | In OBEO, users can now view both XML and MIME source of e-mail messages. |
9342656 | An error message in the Workspaces client was formatted poorly. |
9342862 | After specifying a mobile mapping for a user, the user details could not be opened in Oracle Beekeeper. |
9343594 | When using OBEE on Microsoft Windows 7, changing the name of a workspace in the left-hand box caused Windows Explorer to crash. |
9343799 | In OBEE, opening and then closing folder properties caused the upload file queue to empty without completing the uploads. |
9346202 | Problems with button alignment on localized versions of the Workspaces client were identified and fixed. |
9347047 | An improvement was made in how the system handles an error during importation of time management data from a coexisting system. |
9351524 | An improvement was made to the wiki link rendering APIs in the BDK. |
9353029 | A problem with Oracle Beehive Webmail caching related to client skins caused excessive memory consumption on the server. |
9353361 | Users owning more than one workspace could not list or retrieve Oracle Beehive Voicemail messages using the Touchtone User Interface. |
9355457 | Performance and scalability improvements were made in the Time Management Service. |
9355654 | After deleting a large amount of users in a coexisting Lotus Domino instance, Oracle Beehive user meeting invitation and free/busy lookup connections could not be completed to the Domino server. |
9363697 | In OBEO, if a file is being uploaded and a user attempts to upload another copy of that file, a prompt asks if the user wants to overwrite. Even if the user chose to overwrite, two copies of the document were being created. |
9363917 | Improvements were made to search performance on Oracle Beehive Webmail. |
9364356 | Improvements were made to the BDK documentation for various Email Service calls. |
9364740 | Improvements were made to the BDK documentation for varions Workspace Service calls. |
9371800 | The type ConferenceVariantPermission was missing from the BDK. |
9372330 | A performance improvement for certain kinds of searches was made to the Search service. |
9372787 | A script is now provided to enable Oracle Database Compression functionality for certain Oracle Beehive schema objects. |
9381345 | A performance improvement was made in the Oracle Beehive Workspaces client Profile page. |
9383913 | A rare condition that could lock Oracle Beehive out of database connections was identified and fixed. |
9394795 | In Oracle Beekeeper, after removing a service instance while it had metrics displayed on the metrics dashboard, the dashboard could become unavailable. |
9396242 | A performance issue when looking up an e-mail message using its identifier was fixed. |
9403888 | The Search Service was not processing some e-mail messages. |
9404533 | The Search Service was not indexing e-mails with .ppt and .pdf attachments. |
9407962 | OPMN Patch 9291562 is included in this Patch Set. |
9412002 | Meetings with special characters in the description sent to the Coexistence Connector caused it to stop responding. |
2.0.1.1.0 Patch Set for Oracle Beehive Release 2 (2.0.1.0.0) is available in English only. There are no translations of any English labels and other text.
2.0.1.1.0 Patch Set for Oracle Beehive Release 2 (2.0.1.0.0)
Copyright © 2008, 2010, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Copyright © 2008, 2010, Oracle and/or its affiliates. All rights reserved. |