10g (9.0.4) for Linux x86
Part Number B12261-03
 Home |
 Contents |
| Oracle® Application Server 10g Release Notes 10g (9.0.4) for Linux x86 Part Number B12261-03 |
|
This chapter describes issues with Oracle Enterprise Manager. It includes the following topics:
This section describes general issues and their workarounds for the Oracle Enterprise Manager Application Server Control. It includes the following topics:
When you are making configuration changes within the Application Server Control, the browser keeps track of the state of your editing session. For example, the browser keeps track of the changes you make and your location within on-screen configuration wizards before you click Finish or Apply.
A problem with the browser state can occur if you have installed multiple application server instances on a single host and you open two more browser windows to manage the OC4J instances on the host. If you switch between the windows while making configuration changes, you could experience some unpredictable behavior. For example, the browser may display a message saying that the session has expired.
To avoid this problem, start a new browser instance from the desktop and close any new windows opened from the original browser session.
If you are using Netscape 7 you will need to create a new Netscape Profile for additional browser windows.
In order to collect performance metrics for the OC4J instances in an application server installation, the Oracle HTTP Server for the application server instance must be up and running. If the Oracle HTTP Server component is down, OC4J metrics will not be collected and, as a result, will not be available in the Application Server Control.
The Application Server Control does not support the ability to enter multiple IP address pairs in the Virtual Host directive in the Oracle HTTP Server httpd.conf configuration file.
In other words, do not enter more than the following in the httpd.conf file when using the Application Server Control to manage your Oracle HTTP Server instance:
<VirtualHost 1.2.3.4:5678 9.10.11.12:5679 > ... </VirtualHost>
Oracle Application Server Web Cache provides two ports. One port is the Administration port, which is used to access the Web Cache Manager. The other port is used to gather Web Cache performance statistics.
If you change the protocol for Oracle Application Server Web Cache, you must be sure to use the same protocol for the Administration Port and the Statistics port. If the protocol for these two ports does not match, the Application Server Control may not be able to gather performance metrics and the link to the Web Cache Manager on the Web Cache target home page will not function properly.
OC4J security employs a user manager to authenticate and authorize users and groups that attempt to access a J2EE application. One of the user managers that can be used to designate the users and groups for an application is the JAZN user manager.
With the Enterprise Manager Application Server Control, you can specify that the JAZN user manager be associated with an application. Using the Deploy Application: User Manager page for Enterprise Manager, you can specify that the application use either a JAZN XML configuration or a JAZN LDAP configuration.
When you use Enterprise Manager to specify an XML-based JAZN configuration, the following line is entered into the orion-application.xml file:
<jazn provider="XML" location="./jazn-data.xml" />
When you use Enterprise Manager to specify an LDAP-based JAZN configuration, the following line is entered in the orion-application.xml file:
<jazn provider="LDAP" default-realm="sample_subrealm" location="<<ldap_url>>" />
Some applications may prefer to specify a JAZN configuration by providing a path to a jazn.xml file, but Enterprise Manager does NOT support this type of JAZN configuration. This type of JAZN configuration would be specified as follows in the orion-application.xml file:
<jazn config="jazn.xml"/>
If you manually specify this type of JAZN configuration in the orion-application.xml file, you will either NOT be able to use the Enterprise Manager OC4J Security page or you may experience problems even after apparently using the page successfully.
For more information about using user managers specifying users and groups for a J2EE application, see Oracle Application Server Containers for J2EE Security Guide.
When you are attempting to deploy an OC4J application using the Application Server Control, you may receive the following error:
Deployment failed: Nested exception Root Cause: Lookup error: javax.naming.NoPermissionException: Not allowed to look up java:comp/ServerAdministrator, check the namespace-access tag setting in orion-application.xml for details;
This error may appear if the user manager for the OC4J default application does not include the user admin and the group administrators.
To view or define the users and groups for the default application user manager:
Enterprise Manager displays the OC4J Application home page for the default application.
Enterprise Manager displays the Security page, which lists the Groups and Users.
After you make changes on the OC4J Security page, you must restart the OC4J instance in order for the changes to take effect. For example, if you add the user admin user and the administrators group as described in Section 26.1.6, you must restart the OC4J instance to complete the procedure.
In some cases, you may see the following error message displayed in your browser window:
The SMISession has been invalidated. Resolution: Please close the current SMISession, start another one and reapply the actions
To resolve this issue, click the Refresh Data icon located to the right of the time stamp, or close and reopen the browser to start a new session. This error can be the result of multiple users performing conflicting configuration actions on a single Enterprise Manager Application Server Control at the same time.
If in a non-English environment, you launch a command line tool (for example, opmnctl or emctl) to start a process, make sure the operating system default locale and the NLS_LANG settings are configured properly.
To make sure the default locale is set properly, make sure the LC_ALL or LANG environment variables are set with the appropriate value. To check the current setting, issue the following command:
$PROMPT> locale
For the specific value in each operating system, refer to the platform-specific documentation.
To check the NLS_LANG setting:
$ORACLE_HOME/opmn/conf/opmn.xml
opmn.xml exists, make sure the NLS_LANG setting in the opmn.xml file is identical to the NLS_LANG environment variable.
opmn.xml file:
<environment> <variable id="TMP" value="/tmp"/> <variable id="NLS_LANG" value="JAPANESE_JAPAN.JA16SJIS"/> </environment>
When operations that affect the name, location, or creation of HTTP Server logs are performed (for example, if you create a new HTTP Server virtual host), the Log File Viewer may not reflect these updates. For example, the log files for the newly created virtual host may not appear in the Log Viewer.
This problem is caused because the Log File Viewer may cache information about HTTP Server log files. Press the Refresh Data icon on the Log File Viewer page to workaround this situation and discover the current log files.
Depending upon the version of Internet Explorer and the server platform that the application server is running on, you may not be able to display log files that are stored in XML format.
For example, if you click the name of a log file on the Log File page the Application Server Control may display an error rather than the contents of the log file.
To work around this problem, try using a different browser or browser version to display the XML log file.
In certain situations, deinstallation of Application Server 9.0.2 or 9.0.3 may, through an automatic procedure run at deinstall time, cause a number of configuration files in the Application Server 10g directories to be overwritten with incorrect information.
The Enterprise Manager control scripts in Application Server 10g have been modified to make as-needed backups of these files; as a result, you should be able to recover from this problem by replacing the files from the backup versions.
These files are:
$ORACLE_HOME/sysman/config/iasadmin.properties $ORACLE_HOME/sysman/emd/targets.xml $ORACLE_HOME/sysman/j2ee/config/jazn-data.xml $ORACLE_HOME/sysman/webapps/emd/WEB-INF/config/consoleConfig.xml
There may be a number of backup files in each of these cases. The backups are named in the form <original-file-name>.n, where n is a number from 1 to 10.
The most recent backup of the file is .1, then next most recent .2, and so on. You should check the timestamps or inspect these files to determine which is the most recent correct version of the data. This is most likely the last backup version before you deinstalled Application Server 9.0.2 or 9.0.3.
To restore these files:
$PROMPT> emctl stop iasconsole
$PROMPT> emctl start iasconsole
The following performance notes can help improve the overall performance of the Oracle Enterprise Manager Application Server Control in specific usage situations.
If you attempt to deploy an OC4J application while using Microsoft Internet Explorer or Netscape 7.0, the file upload may take an extremely long time (for example, 10 minutes for a 45MB .ear file as compared to 15 seconds with Netscape 7.1). This has a direct impact on the OC4J deployment wizard performance.
If you are using Netscape Navigator, upgrade to Netscape 7.1.
If you are using Internet Explorer, refer to the following Microsoft knowledge base article, which addresses this problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;329781
When attempting to deploy a large application (greater than 50MB EAR or WAR file), the default configuration for the DCM Daemon is insufficient. Attempting to deploy such a large application will result in an Out Of Memory error.
To resolve this issue, use the Application Server Control to increase the java heap for the DCM Daemon:
opmn.xml file.
-Xmx<nnn>MB
For example:
-Xmx128M
Oracle Application Server includes a version of the Oracle Management Agent that gathers monitoring data for the Application Server Control. If the Management Agent is running out of memory while collecting application server metrics, the memory available to the JVM running within the Management Agent can be increased (default is 64M).
Within the $ORACLE_HOME/sysman/config/emd.properties file, the agentJavaDefines property can have the -Xmx<nnn>M (for example, -Xmx128M) qualifier appended to it to increase the amount of java heap available to the Management Agent JVM. The Management Agent must be restarted for the qualifier to be recognized.
To retrieve cached metrics (metrics which are collected by default and stored in the agents memory) for pages within the Application Server Control, define the environment variable EM_OC4J_OPTS to the following before starting the Application Server Control:
-Doracle.sysman.refreshFlag=true
To disable the processing page so that the Application Server Control waits for start, stop, and other such actions, define the environment variable EM_OC4J_OPTS to the following before starting the Application Server Control:
-Doracle.sysman.eml.util.iAS.waitForCompletion=true
To increase the timeout (default is 2 seconds) for status and host related metric retrieval for non-opmn managed components on the Application Server home page, define the environment variable EM_OC4J_OPTS to the following before starting the Application Server Control:
-Doracle.sysman.ias.ApplicationServerObject.timeout=true
If network interfaces do not show values for "Network Interface Combined Utilization (%)", "Network Interface Read Utilization (%)" and "Network Interface Write Utilization (%)" metrics, create the text file $ORACLE_HOME/sysman/config/network_speed and create entries using the following syntax:
<Interface Name> <Speed in Mbps>
For example, if metrics are not displayed for the interface eth0, add the following entry, where 100 is the network speed in MB per second:
eth0 100
This section describes known errors in the documentation and online help. It includes the following topics:
setupinfo.txt FileThe setupinfo.txt file contains information about the URLs and port numbers you can use to access the Application Server Control, as well as other information about the Oracle Application Server installation.
The online help topic "Displaying the Application Server Control" incorrectly identifies the location of this file after the application server installation. The correct location of the file is:
$ORACLE_HOME/Apache/Apache/setupinfo.txt
On the ports page of the Application Server Control, an additional Oracle HTTP Server Listener row for Oracle HTTP Server Listener with Oracle HTTP Server Diagnostic port may be listed twice. This may happen if you execute an OPMN reload operation after making changes to the opmn.xml file. The double port listing typically occurs when a new OC4J instance is created.
The duplicate row will go away when you restart Oracle HTTP Server.
|
 Copyright © 2003 Oracle. All Rights Reserved. |
|