Skip Headers
Oracle® Beehive Release Notes
Release 1 (1.5)

Part Number E14829-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

6 Administration Notes

This module contains the following types of information regarding Oracle Beehive administration:

General Administration Notes

This section contains general information that is useful to Oracle Beehive administrators, and includes the following topics:

Troubleshooting and Diagnosing Issues with Oracle Beehive

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

Enterprise Manager Grid Control Documentation

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

Oracle Beekeeper Recommended for Configuring E-mail Rules

Oracle recommends that administrators use Oracle Beekeeper to configure E-mail Service rules. If you prefer to use beectl for this purpose, please contact Oracle Support for assistance.

Oracle Beekeeper Compatibility

Each release of Oracle Beekeeper is only compatible with its associated release of Oracle Beehive. For example, Oracle Beekeeper 1.3.1.0.0 is only compatible with Oracle Beehive 1.3.1.0.0, and so on.

Oracle Beehive No Longer Supports Local Updates of JVM Start and Stop Parameters

Prior to Oracle Beehive Release 1 (1.4), Oracle Beehive required administrators to update JVM start and stop parameters for OC4Js and the Oracle Beehive BTI in local copies of the opmn.xml file. However, in Oracle Beehive Release 1 (1.4) and later this method is no longer supported.

To update JVM start and stop parameters, administrators must now enter changes in the Oracle Beehive Central Configuration Repository using the beectl command line tool. Also, after updating any parameters, administrators should execute the modify_local_configuration_files command and restart any OPMN or OC4J instances as necessary. The modify_local_configuration_files command culls updates from the Oracle Beehive Central Configuration Repository and pushes them to local copies of the opmn.xml file.

Running beectl as Root User Not Supported and May Cause Undesired Results

Bug 8838233. Oracle strongly recommends that you do not run the beectl command-line tool as root as this action is not supported and may cause undesired results.

Properties and Preference Set Names are Case Sensitive

All Oracle Beehive property and preference set names are case sensitive. When using the beectl command-line tool to set the value for a property or preference set, ensure that you use the correct case for the property or preference set name.

Known Administration Limitations and Workarounds

This section contains information on known limitations and workarounds related to Oracle Beehive administration, and includes the following topics:

Oracle LogMiner and the SYSAUX Tablespace

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

Password Change May Result in LDAP Synchronization Account Getting Locked Out

Note:

This known 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:

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

  2. Activate the configuration by issuing the following command:

    $ beectl activate_configuration

  3. In the external user directory, change the password of the LDAP account used for synchronization.

  4. Update the Oracle Beehive LDAP configuration file with the account's new password.

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

  6. Activate the configuration by issuing the following command:

    $ beectl activate_configuration

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

Running beectl Commands in Oracle Home as Root User Causes Issues

For 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 Prematurely Causes Issues with Search

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.

Error While Shutting Down Oracle Beehive 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.

OPMN Required for Controlling Oracle Beekeeper's OC4J Instances

Bug 7316433. To control Oracle Beekeeper OC4J instances, administrators need to leverage OPMN. The method for controlling OC4J instances depends on your operating system, as follows:

Table 6-1 Supported Methods for Controlling Oracle Beehive OC4J Instances

Release Method

Oracle Beehive Release 1 (1.5) for Linux

Run $OH/opmn/bin/opmnctl to start and stop an OC4J instance.

Oracle Beehive Release 1 (1.5) for Microsoft Windows (32-bit)

Use one of the following methods:

  • Command shell: Run $OH\opmn\bin\opmnctl to start and stop an OC4J instance, but only do so from a command shell and only after setting the variable OPMN_USE_ORACLELIBS to false within the command shell.

  • Windows Service Manager: Leverage OPMN through Windows Service Manager, either through the GUI provided or from the command line using the Windows net start command.

Note: Logging out of the Microsoft Windows computer where Oracle Beekeeper resides will terminate the administration tool.

Oracle Beehive Release 1 (1.3.2) for Solaris Operating System (SPARC 64-bit)

Run $OH/opmn/bin/opmnctl to start and stop an OC4J instance.


Date and Time Formats in Oracle Beekeeper May Not Display Correctly in Multi-byte Languages

Note:

This issue applies to Oracle Beehive Release 1 (1.3.2.0.0) for Solaris Operating System (SPARC 64-bit) and later.

Bug 7328539. In Oracle Beekeeper, 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.

Restarting Oracle Beehive Application Tier Instances Requires Restart of Oracle Beekeeper OC4J Instances

Bug 8332399. If you restart an Oracle Beehive application tier instance, you must also restart any OC4J instances for Oracle Beekeeper residing in the same site.

Oracle Beekeeper Does Not Return Users to Login Page After Session Timeouts

Bug 6835314 and 7023557. Oracle Beekeeper 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 Beekeeper instance to 3600 seconds or higher.

Oracle Beehive Does Not Provide Statistics for External Components

Bug 7519613. Through supported administration clients, Oracle Beehive provides administrators with data for a variety of statistical measures, such as counts for login successes and failures. However, Oracle Beehive does not provide statistical data for external components that might be deployed with the system. For example, counts for login successes and failures are not provided for Oracle Enterprise Single Sign-On.

Upgrading to Oracle Beekeeper Release 1 (1.5) Changes Protocol Setting

Bug 8301211. The Oracle Beekeeper upgrade utility provided by Oracle Beehive Release 1 (1.5) changes the protocol setting for Oracle Beekeeper from "https" to "http".

To correct this change, do the following:

  1. Open the default-web-site.xml file, located in the following Oracle Beekeeper directory:

    home/j2ee/home/config

  2. Change the value of the protocol setting from "http" to "https".

  3. Save default-web-site.xml.

  4. Restart Oracle Beekeeper.

beectl and Oracle Beekeeper Expose Deprecated Search Service Properties

Bug 7028998. The beectl command-line utility and Oracle Beekeeper expose the following Search Service properties although these properties are no longer supported by Oracle Beehive:

  • CrawlCalendarsEnabled

  • CrawlDocumentsEnabled

  • CrawlEmailsEnabled

Attempting to enable or disable these properties has no effect on the system as this functionality is now provided by default when the Search Service is enabled.

Known Administration Issues

This section contains information about known issues related to Oracle Beehive administration, and includes the following topics:

Entering Unsupported Property Values in Oracle Beekeeper May Result in Generic Error Messages

Bug 7241913. Entering unsupported values for properties in Oracle Beekeeper may result in generic error messages that do not identify the source of the issues. For example, the Next Command Timeout property (under SMTP Properties - InboundVMS) only supports positive integers. If you enter a value of "0" for this property, an error message will appear implying an "unexpected method invocation exception" occurred, rather than a message that states that "0" is an invalid entry for this property.

Oracle Beehive May Not Update Users' Timezone Attribute After LDAP Synchronization

Note:

This issue is resolved in Oracle Beehive Release 1 (1.5.1.2) and later.

Bug 8341466. If a TimeZone map is created in the LDAP sync profile after the users have been synchronized from LDAP, it will not cause the users' timezone attribute values to be updated in Oracle Beehive.

Oracle Beekeeper Generates Additional Login Event Entries

Bug 8305263. Oracle Beekeeper generates a login event entry each time a page refreshes in the administration tool. This results in additional login event entries in the Audit repository for each deployment. These entries do not impact the normal functioning of Oracle Beekeeper or Oracle Beehive, and, therefore, can be ignored.

Unable to Purge Users Who Have Offline Instant Messages

Note:

This issue only applies to deployments that originally installed Oracle Beehive Release 1 (1.2) or Release 1 (1.3). If your organization first deployed Oracle Beehive Release 1 (1.4) or later, the issue described here does not apply.

Bug 8362518. Attempts to purge users who have offline instant messages will fail.

Attempting to Execute the modify_hostname Command May Fail

Bug 8445542. Attempting to execute the modify_hostname command and some its options may fail. If you need to execute the modify_hostname command, please contact Oracle Support.