| Oracle® Beehive Release Notes Release 1 (1.4) Part Number E13790-07 |
|
|
View PDF |
| Oracle® Beehive Release Notes Release 1 (1.4) Part Number E13790-07 |
|
|
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 No Longer Supports Local Updates of JVM Start and Stop Parameters
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
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.
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.
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.
This section contains information on known limitations and workarounds related to Oracle Beehive administration, and includes the following topics:
Password Change May Result in LDAP Synchronization Account Getting Locked Out
Running beectl Commands in Oracle Home as Root User Causes Issues
OPMN Required for Controlling Oracle Beekeeper's OC4J Instances
Date and Time Formats in Oracle Beekeeper May Not Display Correctly in Multi-byte Languages
Oracle Beekeeper Does Not Return Users to Login Page After Session Timeouts
Oracle Beekeeper Does Not Provide Interface to Key Virus Scanning Options
Services Intermittently Disappear from View in Oracle Beekeeper
list_statistics Command Not Supported by the Access Control Service and all_components Option
Oracle Beehive Does Not Provide Statistics for External Components
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 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:
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.
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.
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 OC$J Instances
| Release | Method |
|---|---|
|
Oracle Beehive Release 1 (1.3.1) for Linux |
Run |
|
Oracle Beehive Release 1 (1.3.2) for Microsoft Windows (32-bit) |
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. Also, 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. |
|
Oracle Beehive Release 1 (1.4.1 and later) for all operating systems |
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) 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.
Note:
This issue applies to Oracle Beehive Release 1 (1.3.2.0.0) for Solaris Operating System (SPARC 64-bit) and later.Bug 7328615. The tab for managing devices in Oracle Beekeeper is blank. Administrators can access this tab in the Enterprises panel of Oracle Beekeeper.
Bug 7314072. If you restart an Oracle Beehive application tier instance, you must also restart any OC4J instances for Oracle Beekeeper residing in the same site.
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.
Bug 7198267. The Simple Search field in Oracle Beekeeper 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 Beekeeper, 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. Oracle Beekeeper 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.
Bug 7390676. The list of services that normally appears in the left-hand pane of Oracle Beekeeper may disappear on an intermittent basis. If this occurs, restart the stand-alone OC4J for Oracle Beekeeper and the list will appear again.
Bug 7244892. The list_statistics command is not supported by the Access Control Service and the all_components option. Executing the list_statistics command for this service or all components will result in an error.
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.
Bug 7426636. The "Use simple relay mode" option provided by Oracle Beekeeper is not yet supported. This option appears in the Transport Properties tab of the Configuration interface for the E-mail Service.
If your deployment leverages a relay server, do not enable the "Use simple relay mode" option or enter a relay server in the Relay Server field. Instead, enter the fully qualified domain name and port number of your relay server in the Relay Host field, located in the Delivery Routing section of Transport Properties tab.
Note:
This issue applies to Oracle Beehive Release 1 (1.4) and later in deployments that leverage LDAP-based authentication through Oracle Internet Directory only.Bug 8237631. Oracle Beehive Release 1 (1.4) and later provide a configuration file (jps-config.xml) that contains invalid settings. jps-config.xml is used to configure LDAP-based authentication for Oracle Beehive deployments that leverage Oracle Internet Directory. If your deployment leverages Oracle Internet Directory in this way, Oracle strongly recommends that you change the settings in jps-config.xml to values that are valid for your deployment.
To change the settings in jps-config.xml, please refer to the following topics:
"Configuring Oracle Beekeeper for LDAP-Based Authentication" in the Oracle Beehive installation guide for your operating system.
"Oracle Beehive Installation Guides Contain Incorrect Path for jps-config.xml" in this document.
This section contains information about known issues related to Oracle Beehive administration, and includes the following topics:
Attempting to Update Device Type Profile in Oracle Beekeeper May Result in Error
Entering Unsupported Property Values in Oracle Beekeeper May Result in Generic Error Messages
Bug 7006108. Any resources that are created and specified as "external" do not appear in the Resources panel of Oracle Beekeeper.
Bug 7028411. Administrators may be unable to create resources in Oracle Beekeeper, 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 Oracle Beekeeper 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 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.
Bug 8235711. The version number that appears in Oracle Beekeeper 1.4.3.1 is 1.4.3.0.12559. The version number should be 1.4.3.1.
|
 Copyright © 2008, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|