| Oracle® Beehive Release Notes Release 1 (1.2 and 1.3) Part Number E10487-09 |
|
|
View PDF |
| Oracle® Beehive Release Notes Release 1 (1.2 and 1.3) Part Number E10487-09 |
|
|
View PDF |
This module contains the following types of information regarding Oracle Beehive administration:
This section contains general information that is useful to Oracle Beehive administrators, and includes the following topics:
Using ESCAPE to Prepend Special Characters When Adding or Removing E-mail Addresses
Oracle Beehive Administration Console Recommended for Configuring E-mail Rules
When attempting to troubleshoot or diagnose issues related to Oracle Beehive, please refer to the infrastructure (core) log file of the OC4J instance where Oracle Beehive is deployed. This log file provides the most useful information if issues occur, especially workspace-related issues. Also, Oracle recommends referring to this file whenever you communicate with Oracle Support Services to diagnose and resolve issues.
Typically, you can access this log file in the following location:
$ORACLE_HOME/beehive/logs/oc4j/BEECORE/log.txt
For connectivity issues, refer to the log files in the following location:
$ORACLE_HOME/beehive/logs/bti/
The main application log file is in the following location:
$ORACLE_HOME/beehive/logs/oc4j/BEEAPP/log.txt
Command-line events are captured in log files in the following location:
$ORACLE_HOME/beehive/logs/beectl/
Management events are captured in log files in the following location:
$ORACLE_HOME/beehive/logs/oc4j/BEEMGMT
When using beectl to add or remove e-mail addresses from user accounts, the + and - characters (used to indicate add and remove) need to be escaped. This can be accomplished by prepending these characters with "ESCAPE:" (on all operating systems) or "\\" (on the Linux and Solaris operating systems only).
For example, to remove the mailto address (business_1) for a user (user1) with Oracle Beehive running on a supported Windows operating system, enter the following command:
$ beectl modify_user --user loginid=user1 --address ESCAPE:-business_1:mailto:user1@example.com
With Oracle Beehive running on a supported Linux or Solaris operating system, administrators may enter the previous command or the following command:
$ beectl modify_user --user loginid=user1 --address \\-business_1:mailto:user1@example.com
For documentation on Enterprise Manager Grid Control, including release notes that are specific to that product, please refer to the following link:
http://download.oracle.com/docs/cd/B16240_01/doc/nav/portal_booklist.htm
The Oracle Beehive Administration Console 1.3.1.0.0 is only compatible with Oracle Beehive 1.3.1.0.0.
Oracle recommends that administrators use the Oracle Beehive Administration Console to configure E-mail Service rules. If you prefer to use beectl for this purpose, please contact Oracle Support for assistance.
This section contains information on known limitations and workarounds related to Oracle Beehive administration, and includes the following topics:
After Oracle Beehive Database Restart, Must Restart Oracle Beehive
Password Change May Result in LDAP Synchronization Account Getting Locked Out
Running beectl Commands in Oracle Home as Root User Causes Issues
After Oracle Beehive Database Restart, Must Restart Oracle Beehive
Unable to List Users with beectl and the Oracle Beehive Administration Console
OPMN Required for Controlling the Oracle Beehive Administration Console's OC4J Instances
Device Management Tab in Oracle Beehive Administration Console is Blank
Oracle Beehive Administration Console Does Not Return Users to Login Page After Session Timeouts
Requirements for LDAP Profile Changes Through Oracle Beehive Administration Console
Oracle Beehive Administration Console Does Not Provide Interface to Key Virus Scanning Options
Bug 6720427. Oracle Beehive uses Oracle LogMiner extensively, which enables you to query online and archived redo log files through an SQL interface. By default, Oracle LogMiner stores its data in the SYSAUX tablespace.
By default, the SYSAUX tablespace contains one datafile (bigfile) in auto-extensible mode. This means that if SYSAUX is almost out of space, the RDBMS kernel will physically increase the size of the datafile, which is a time-consuming operation.
To prevent this operation from occurring too frequently, perform one of the following recommendations:
Make sure that there is enough space in the SYSAUX tablespace and apply the recommendations in OracleMetaLink note 429599.1, "How to Reduce the Highwater of LOGMNR_RESTART_CKPT$ in 10.2"
or,
Make sure that there is enough space in SYSAUX and increase the size of disk space to be allocated automatically when more extends are required. (The default is the size of one data block). Specify this size in the NEXT clause of the autoextend_clause in the SQL statement ALTER DATABASE
or,
Call the DBMS_LOGMNR_D.SET_TABLESPACE procedure to re-create all LogMiner tables in an alternate tablespace. Ensure that the alternate tablespace has the characteristics specified in recommendation 2 (specifying a larger amount of disk space to be allocated when more extends are required).
Note:
This limitation only affects deployments that leverage an external user directory, such as Oracle Internet Directory, Microsoft Active Directory, and Sun Java Directory Server.In cases where an external user directory is used, changing the password of the LDAP account used for synchronization (not the password of a regular user account) may result in that account getting locked out. This will occur if Oracle Beehive attempts to authenticate multiple times using the stored (old) password.
To avoid this situation, complete the following steps whenever you change the password of the LDAP account used for synchronization:
Disable the synchronization directory profile by issuing the following command:
$ beectl modify_property --component <profile_name> --name ProfileState --value DISABLE
For example:
$ beectl modify_property --component oidldapdirectoryprofile --name ProfileState --value DISABLE
Activate the configuration by issuing the following command:
$ beectl activate_configuration
In the external user directory, change the password of the LDAP account used for synchronization.
Update the Oracle Beehive LDAP configuration file with the account's new password.
Enable the synchronization directory profile by issuing the following command:
$ beectl modify_property --component <profile_name> --name ProfileState --value ENABLE
For example:
$ beectl modify_property --component oidldapdirectoryprofile --name ProfileState --value ENABLE
Activate the configuration by issuing the following command:
$ beectl activate_configuration
Issue the modify_local_configuration_files command.
For more information on this and other commands issued in this procedure, please refer to Oracle Beehive Administrator's Reference Guide.
beectl Commands in Oracle Home as Root User Causes IssuesFor Oracle Beehive instances in the UNIX and LINUX operating systems, running any beectl commands in your Oracle home as the root user may cause issues. Oracle strongly recommends that you do not run any beectl commands in your Oracle home as the root user. Instead, you should always run commands as the user who installed your Oracle Beehive instance.
Deleting archive logs before the Oracle Database Change Data Capture (CDC) service has processed them will causes issues. If this occurs, please contact Oracle Support Services for information on how to resolve your situation.
Bugs 6664265 and 6726307. If you restart the Oracle Database instance associated with Oracle Beehive, such as after an unplanned database outage, users may experience one or more issues. This may include not being able to log in to the system or beectl commands issued in previously-opened beectl shells failing. To resolve these and other potential issues, it is recommended that you restart Oracle Beehive whenever you restart its associated database.
Bug 6751859. Shutting down an Oracle Database instance associated with your Oracle Beehive deployment may result in the following error:
ORA-00600: internal error code, arguments: [LibraryCacheNotEmptyOnClose], [], [], [], [], [], [], []
Ignore this error as it indicates that some items remain in the library cache when closing down the instance. The error itself occurs after the database close and dismount stages so it only affects the instance shutdown itself. All datafiles have been closed cleanly and no additional steps are required.
Note:
This issue is resolved in Oracle Beehive Release 1 (1.3) and later.Bug 6830699. If a user attempts to connect to the system over SSL with a certificate that is not trusted by the user's operatin g system, such as with a dummy certificate, the user may receive an error message that indicates the presence of an invalid server. However, the message does not indicate that the certificate is invalid or not trusted. To avoid this issue, only use certificates that are trusted by the wallets of your users' operating systems. Typically, certificates are required for secure connections with Oracle Beehive Integration for Outlook and the Oracle Beehive mobile device plug-in.
Note:
This issue applies to Oracle Beehive Release 1 (1.3.1) for Linux only.Bugs 7304020 and 7307849. Administrators running Oracle Beehive Release 1 (1.3.1) for Linux will be unable to list users in the Oracle Beehive Administration Console. This issue also occurs with the beectl command line utility if you use the --family_name or --given_name option with the list_users command. This issue is resolved by Patch #7309600, which is available on Oracle MetaLink (metalink.oracle.com). Oracle recommends that administrators of Linux-based deployments install this patch.
Bug 7316433. To control Oracle Beehive Administration Console OC4J instances, administrators need to leverage OPMN. The method for controlling OC4J instances depends on your operating system, as follows:
Oracle Beehive Release 1 (1.3.1.0.0) for Linux: Supported methods for starting and stopping the OC4J instance include the $OH/bin/oc4j command or any user-created method for running java -jar oc4j.jar.
Oracle Beehive Release 1 (1.3.2.0.0) for Microsoft Windows (32-bit): Administrators can run $OH/opmn/bin/opmnctl to start and stop an OC4J instance, but they may only do so only from a command shell and only after setting the variable OPMN_USE_ORACLELIBS to false within the command shell. Also, logging out of the Microsoft Windows computer where the Oracle Beehive Administration Console resides will terminate the administration tool.
Oracle Beehive Release 1 (1.3.2.0.0) for Solaris Operating System (SPARC 64-bit): Administrators can run $OH/opmn/bin/opmnctl to start and stop an OC4J instance.
Note:
This issue applies to Oracle Beehive Release 1 (1.3.2.0.0) for Solaris Operating System (SPARC 64-bit) only.Bug 7328539. In the Oracle Beehive Administration Console, the date and time formats may not display correctly in multi-byte languages, such as Chinese, Korean, and Japanese. In these cases, other characters, such as question marks (?), may replace characters in date and time entries. This includes the characters that are used to represent "AM" and "PM" in these locales.
Note:
This issue applies to Oracle Beehive Release 1 (1.3.2.0.0) for Solaris Operating System (SPARC 64-bit) only.Bug 7328615. The tab for managing devices in the Oracle Beehive Administration Console is blank. Administrators can access this tab in the Enterprises panel of the Oracle Beehive Administration Console.
If you restart an Oracle Beehive application tier instance, you must also restart any OC4J instances for the Oracle Beehive Administration Console residing in the same site.
Bug 6835314. The Oracle Beehive Administration Console does not return users to the Login page after session timeouts. To minimize the risk of experiencing this issue, Oracle recommends that you set the session timeout value for your Oracle Beehive Administration Console instance to 3600 seconds or higher.
Note:
This issue does not affect the Advanced Search dialog window in the Oracle Beehive Administration Console.Bug 7198267. The Simple Search field in the Oracle Beehive Administration Console does not automatically handle strings that contain one or more colons (:). As a result, searching for a string that contains one or more colons, such as a collabID, will result in an error. To avoid this issue, enclose in quotation marks any search strings that contain colons when using the Simple Search field.
Bugs 7204616 and 7274297. Changing LDAP profiles through Oracle Beehive Administration Console, such as adding, modifying, or deleting LDAP profiles, requires certain additional steps for any new configurations to apply correctly. For example, to add a new profile, you must ensure that the default flag is set at the time that the new profile is created. Otherwise, the profile will not work. Also, if you delete a profile, you must activate the configuration before creating a new profile. Failing to complete these additional steps may result in system errors.
Bug 7257339. The Oracle Beehive Administration Console does not provide an interface to the following options, which are mandatory to correctly enable the system's virus scanning features:
add_virus_scan_engine
modify_virus_scan_policy
Oracle recommends that you use beectl to set these options.
This section contains information about known issues related to Oracle Beehive administration, and includes the following topics:
modify_user Command Allows Unregistered Properties on User Accounts
Running list_properties Command on LDAP Server Displays Certain Invalid Properties
Running import_documents Command Multiple Times Creates Empty Files
External Resources Do Not Appear in Oracle Beehive Administration Console
E-mail Processing Attribute in Oracle Beehive Administration Console Does Not Function
Attempting to Remove Metrics from Oracle Beehive Administration Console Dashboard Results in Error
Note:
This issue is resolved in Oracle Beehive Release 1 (1.3) and later.Bug 6859628. Administrators can add unregistered properties to user accounts through the modify_user command, although beectl should prohibit this action. Instead, beectl should only allow administrators to add registered properties to user accounts. To register a property for use with user accounts, use the add_custom_user_property command.
Bug 6897031. Running the list_properties command on an LDAP server will display the following invalid properties: ssl_mode and profile_mode.
Bug 6523854. Running the import_documents command multiple times will create empty files (files that contain zero bytes) even when the conflict_resolution_mode property is set to OVERWRITE. Although the import_documents command is intended as a one-time import procedure, the command currently does not function as expected when issued multiple times.
Bug 6927453. When used with the upload_client_application command, the --community option is intended to provision a client application to a specified community. While the option works correctly in this regard, it may also unintentionally deprovision other applications associated with the same community. Therefore, Oracle recommends that you do not use the --community option with the upload_client_application command at this time. After uploading an application, you can safely provision it to a community by using the --community option with the add_client_application_provisioning command instead.
For more information on the upload_client_application and add_client_application_provisioning commands, please refer to the Oracle Beehive Administrator's Reference Guide.
Bug 7006108. Any resources that are created and specified as "external" do not appear in the Resources panel of the Oracle Beehive Administration Console.
Bug 7028411. Administrators may be unable to create resources in the Oracle Beehive Administration Console, even if they have the required "resource manager" privileges. Attempting to create a resource may result in an error message that states you "do not have the required access."
Bug 7136764. Attempting to update the profile for a device type in the Oracle Beehive Administration Console may result in an error. This issue tends to occur in cases where the Software Version attribute for a device type contains alphanumeric and special characters.
Bug 7173702. In the Oracle Beehive Administration Console, the Enable E-mail Processing attribute does not function. The system processes and delivers e-mail messages whether or not this attribute is enabled.
Bug 7278431. In the box view of the Metrics Dashboard in the Oracle Beehive Administration Console, attempting to remove a metric from the dashboard will result in an error.
