|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B25335-02 |
|
 Previous |
|
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium B25335-02 |
|
|
Previous |
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 10g Application Server Control Console. It includes the following topics:
Section 20.1.3, "Timestamp on Log Files May Not Be Accurate"
Section 20.1.4, "Errors When Configuring Components or Adding or Removing OC4J Instances"
Section 20.1.6, "Problems with the Progress Page When Using a Macintosh Browser"
Section 20.1.7, "Topology Viewer Applet Fails in OracleAS Cold Failover Cluster Configuration"
Section 20.1.8, "Error When Clicking Topology Link from Host Page"
Section 20.1.9, "Error When Using the ADF BUSINESS COMPONENT Link on the Host Page"
Section 20.1.11, "Incorrect Status Reported for Oracle Business Intelligence Discoverer"
Section 20.1.12, "Changing From JAZN LDAP User Manager Requires OC4J Restart"
Section 20.1.17, "Cannot Recover Database Control Files from the Application Server Control Console"
Section 20.1.19, "Configuring Security When Oracle Application Server Is Managed by Grid Control"
If in a non-English environment, you launch a command line tool such as emctl to start a process, make sure the operating system locale and NLS_LANG environment variable settings are configured properly and consistently. This is applicable to the emctl command line utility that is available with Oracle Application Server installations as well as with the emctl utility available with Grid Control Console installations.
If these environment variables are not set prior to Oracle Application Server or Grid Control Console installations, then non-ASCII characters will appear incorrectly in the Application Server Control Console or Grid Control Console, respectively. To prevent this problem from occurring, set these two environment variables prior to installation. If this is not possible, then to resolve the problem set the two environment variables after installation and restart the Management Agent.
Refer to the following sections for details on how to check and set the values for these variables:
Section 20.1.1.3, "Checking the NLS_LANG Environment Variable"
Section 20.1.1.4, "Setting the NLS_LANG Environment Variable"
Make sure the LC_ALL or LANG environment variables are set with the appropriate value. To check the current setting, issue the following command:
set L
This command lists all the environment variables which start with L. From the list, check if LC_ALL and LANG variables have been set or not.
If you are using the command prompt, then issue the set command:
set LANG zh_CN
Make sure the NLS_LANG environment variable is set with the appropriate and compatible value with the operating system locale setting (and the Grid Control Management Repository database character set if Grid Control is being used to centrally manage the Oracle Application Server). For the specific value for the language or the character set, refer to the Globalization Support Guide of the Oracle product you are using.
In addition, check to see if the NLS_LANG setting exists in %ORACLE_HOME%\opmn\conf\opmn.xml. For example, the following content should appear in the opmn.xml file:
<environment> <variable id="TMP" value="/tmp"/> <variable id="NLS_LANG" value="JAPANESE_JAPAN.JA16SJIS"/> </environment>
If the NLS_LANG setting exists, make sure the NLS_LANG setting in the opmn.xml file is identical to the NLS_LANG environment variable.
Changes applied on the OC4J Server Properties page to an OC4J instance within an Oracle Application Server cluster will always show the message Server properties have been applied across the cluster. In fact, changes to environment variables, ports, islands, and number of island processes will only be applied to the current OC4J instance currently under administration and not to other OC4J instances within the cluster. Other values on this page (for example, Java Options) will be applied across the cluster.
Information concerning which values are applied cluster wide is displayed in a tip at the top of the page; however, the confirmation message may be incorrect.
The log file timestamps shown by the operating system (and displayed in Log Viewer of the Application Server Control Console) are not always correct. The log file may contain recent log messages but the timestamp visible from operating system is frequently older than the last message written to the file.
If you install Oracle Management Agent 10.1.0.2 on a computer which has one or more instances of Oracle Application Server 10g (10.1.2), then you may encounter errors in Application Server Control Console if you later modify your component configuration in the Oracle Application Server installation. For example, you may receive errors if you create or remove an OC4J instance or if you configure an Oracle Application Server component after you have installed the application server.
To workaround this problem, install the Oracle Management Agent 10.1.0.3 or later patchsets.
When using the Apple Safari browser on a Macintosh computer, it is not possible to use the Application Server Control Console to configure or change the Identity Management configuration for an Application Server middle-tier installation.
Specifically, the problem occurs when you click Configure in the Identity Management section of the Infrastructure page in the Application Server Control Console. You can enter the host and port for the Identity Management host, but you cannot display the next page in the wizard.
In addition, the performance charts on the Application Server Home page do not display correctly in the Macintosh browser. Instead of a chart, small question marks appear in their place.
To fix this problem, perform the following procedure:
Stop the Application Server Control service for this Oracle home.
Use a text editor to open the following configuration file in the Oracle Home of the application server instance you are attempting to modify:
%ORACLE_HOME%\sysman\j2ee\config\emd-web-site.xml
Locate the following entry in the file:
<!-- The default web-app for this site, bound to the root --> <default-web-app application="em" name="default" /> <web-app application="em" name="emd" root="/emd" load-on-startup="true" />
Add the following argument to the <web-app> tag:
shared="true"
For example:
<!-- The default web-app for this site, bound to the root -->
<default-web-app application="em" name="default" />
<web-app application="em" name="emd" root="/emd"
load-on-startup="true" shared="true"/>
Save your changes and close the em-web-site.xml file.
Use the Services control panel to start the Application Server Control service for this Oracle home.
Often, when you perform an operation with the Application Server Control Console, such as creating a new OC4J instance, Enterprise Manager displays a progress page, which indicates that the operation is still in progress.
When using the Apple Safari browser on a Macintosh computer, the progress page continues to display even after the operation is complete. As a result, the operation confirmation page does not display as it should.
To solve this problem, set the EM_OC4J_OPTS environment variable to the following value and restart the Application Server Control:
-Doracle.sysman.emSDK.eml.util.iAS.waitForCompletion=true
|
See Also: Appendix "Managing and Configuring Application Server Control" of the Oracle Application Server Administrator's Guide for more information about using theEM_OC4J_OPTS environment variable
|
The Java applet version of the Topology Viewer fails to connect to the Oracle Process Manager and Notification Server (OPMN) if you access Application Server Control with the virtual hostname in a OracleAS Cold Failover Cluster configuration.
Use one of the following workarounds:
Use the HTML Only version of the Topology Viewer.
Connect to the Application Server Control with the physical hostname.
In the Host page of Application Server Control, when clicking the Topology link, the following error appears:
Could not determine the oracle home for this component
To workaround this error, navigate to the Farm page, and click the Topology link from that page.
In the Host page of Application Server Control, when clicking the ADF BUSINESS COMPONENTS target in the Targets section, the following error appears:
Error: Failed to connect to OC4J null instance now, please click refresh page to try again!
To avoid this error, navigate to the OC4J Administration page, and click the ADF Business Components link in the Related Links section.
In some installations, the Farm locator link is lost in Application Server Control Console once you navigate to the Application Server Home page and click Configure Component just above the System Components table to configure a component. Locator links display at the top of pages in Application Server Control Console. They specify the location of the current page within Application Server Control Console. As the user navigates through hierarchical content, or drills down through levels of content and functions, locator links track the location, and allow the user to navigate back to higher levels in the hierarchy.
To get back to the Farm page, navigate to the Application Server Home page, and click the Farm link in the General section.
When managing OracleBI Discoverer with Grid Control Console release 10.1, the Grid Control Console displays inaccurate status for OracleBI Discoverer. For instance, when the component is actually up, the Grid Control Console displays the status as down. A one-off patch to the Grid Control Console Management Agent release 10.1.0.4 will soon be released to Oracle MetaLink to resolve this specific problem.
This problem does not manifest in the Application Server Control Console release 10.1.2. The status for OracleBI Discoverer is displayed correctly in the Application Server Control Console.
If you use the OC4J Application Properties page to change the User Manager for an OC4J application, then note the following: The application will start using the JAZN LDAP User Manager immediately after you select Use JAZN LDAP User Manager and click Apply.
However, if you change from a JAZN LDAP user manager to another User Manager, such as the JAZN XML User Manager, you must restart the OC4J instance before the new User Manager is available to the application.
After you configure security for the Application Server Control, you may see intermittent issues with form data updates in the Logging pages. These issues may occur with Microsoft Internet Explorer browsers after you install the 832894 (MS04-004) security update or the 821814 hotfix. Microsoft Internet Explorer has known issues with using a form on a HTTPS Web page. Problem related to these updates have been seen in the Advanced Search feature of the Search Log Repository page.
To workaround this problem, download the Microsoft Q831167.exe package and any other recommended related patch recommend by Microsoft.
If an Oracle Application Server 10g Release 2 (10.1.2) target is removed from the Grid Control Console, the Infrastructure page in the Application Server Control Console will still show Central Management as Configured.
To reset the Central Management section of the page, delete the following file from the centralagents.lst in the application server Oracle home:
%ORACLE_HOME%\sysman\emd\centralagents.lst (Windows)
You can use the Application Server Control Console to change the password for a component schema in the OracleAS Metadata Repository.
However, when you perform this task in the Application Server Control Console, the new password you enter will be saved in clear text format in the following log file:
%ORACLE_HOME%\sysman\log\em-web-access.log
In addition, if the Application Server Control Console has not been secured, the new schema password will be transmitted unencrypted from the client-side browser to the machine where the Console is running.
|
See Also: "Configuring Security for the Application Server Control Console" in the chapter " Enabling SSL in the Infrastructure" in the Oracle Application Server Administrator's Guide for more information about the benefits of configuring security for the Application Server Control Console |
To avoid these potential security issues, perform the following procedure before changing a schema password in the Application Server Control Console:
Stop the Application Server Control.
You can stop the Application Server Control by stopping the Application Server Control service in the Services control panel.
|
See Also: The "Starting and Stopping" chapter of the Oracle Application Server Administrator's Guide |
Secure the Application Server Control by entering the following command:
%ORACLE_HOME%\bin\emctl secure iasconsole
|
See Also: "Configuring Security for Enterprise Manager Application Server Control Console" in Appendix A of Oracle Application Server Administrator's Guide |
Use a text editor to open the following configuration file in the application server Oracle home:
%ORACLE_HOME%\sysman\j2ee\config\emd-web-site.xml
Locate the following entry in the emd-web-site.xml file:
<!-- Access Log, where requests are logged to --> <access-log path="..\..\log\em-web-access.log" />
Modify the access-log path entry so it describes the format of each log entry, as follows:
<!-- Access Log, where requests are logged to -->
<access-log path="..\..\log\em-web-access.log"
format="$ip - [$time] '$path' $status $size"/>
Save and close the emd-web-site.xml file.
Start the Application Server Control.
You can start the Application Server Control by starting the Application Server Control service in the Services control panel.
|
See Also: The "Starting and Stopping" chapter of Oracle Application Server Administrator's Guide |
When you use Application Server Control Console to monitor targets such as OracleAS Portal that has been configured to use Secure Sockets Layer (SSL), some performance metrics for OracleAS Portal may not display.
To correct this problem you must allow the Application Server Control to recognize the Certificate Authority that was used by the Web Site to support HTTPS. You must add the Certificate of that Certificate Authority to the list of Certificate Authorities recognized by the Application Server Control.
To configure Application Server Control to recognize the Certificate Authority:
Obtain the Certificate of the Web Site's Certificate Authority, as follows:
In Microsoft Internet Explorer, connect to the HTTPS URL of the application server you are attempting to monitor.
Double-click the lock icon at the bottom of the browser screen, which indicates that you have connected to a secure Web site.
The browser displays the Certificate dialog box, which describes the Certificate used for this Web site. Other browsers offer a similar mechanism to view the Certificate detail of a Web Site.
Click the Certificate Path tab and select the first entry in the list of certificates.
Click View Certificate to display a second Certificate dialog box.
Click the Details tab on the Certificate window.
Click Copy to File to display the Certificate Manager Export wizard.
In the Certificate Manager Export wizard, select Base64 encoded X.509 (.CER) as the format you want to export and save the certificate to a text file with an easily-identifiable name, such as portal_certificate.cer.
Open the certificate file using your favorite text editor.
The content of the certificate file will look similar to the content shown in Example 15–1.
Update the list of Certificate Authorities, as follows:
Locate the b64InternetCertificate.txt file in the following directory of the Oracle Application Server Oracle home:
%ORACLE_HOME%\sysman\config\
This file contains a list of Base64 Certificates.
Edit the b64InternetCertificate.txt file and add the contents of the Certificate file you just exported to the end of the file, taking care to include all the Base64 text of the Certificate including the BEGIN and END lines.
Copy the text file that contains the certificate (for example, the file you named portal_certificate.cer earlier in this procedure) to the OracleAS Portal middle tier.
Use the orapki utility to update the monwallet Oracle wallet by using the following command:
%ORACLE_HOME%\bin\orapki wallet add -wallet ORACLE_HOME\sysman\config\monwallet -trusted_cert -cert certificate_location
When you are prompted for a password, enter the password for the monwallet wallet. The default password is welcome.
In the example, replace certificate_location with the full path to the text file that contains the certificate you saved earlier in this procedure and that you copied to the OracleAS Portal middle tier. For example:
D:\oracle\portal_certificate.cer
Restart the Application Server Control.
After you restart the Application Server Control, Enterprise Manager detects your addition to the list of Certificate Authorities and you can successfully monitor the OracleAS Portal metrics using the secure Application Server Control Console.
If you back up an OracleAS Infrastructure Oracle home, you will notice that when you attempt to recover the backup, the option for recovering the OracleAS Metadata Repository database control files is not available on the Perform Recovery page of the Application Server Control Console.
As a result, you cannot recover the database control files that you backed up by using the Application Server Control Console. Instead, use the command-line OracleAS Backup and Recovery Tool to recover the database control files. Specifically, to recover the database control files, use the -c command-line argument to the Backup and Recovery tool.
For more information, see "Restoring and Recovering the Metadata Repository" in Oracle Application Server Administrator's Guide.
If the default language is set to French or French-Canadian, and you select an operation from the contextual menu next to the OracleAS Farm icon in the Application Server Control Console Topology Viewer, a JavaScript error occurs.
To workaround this problem, use the contextual menu associated with the individual instances in the OracleAS Farm.
For more information about using the contextual menus in the Topology Viewer, see "Actions You Can Perform Using the HTML Only Topology Viewer" in the Enterprise Manager online Help.
If you are managing Oracle Application Server with Oracle Enterprise Manager 10g Grid Control, keep in mind the following restriction if you decide to enable security for the Application Server Control after you begin managing the application server with Grid Control.
After you enable security for the Application Server Control, the Administer link on the Application Server Home page in the Grid Control Console will no longer work. Instead of linking to the new HTTPS URL for the secure Application Server Control, the Administer link is still configured to link to the original HTTP URL.
To remedy this problem, you must remove the application server target from the Grid Control Console and then add the target again. For information about removing and adding monitored targets, see the Grid Control Console online help.
If you navigate to the Application Server Control Console and Microsoft Internet Explorer displays a blank screen instead of the Application Server Control Console, the problem is likely caused by the Internet Explorer Allow META REFRESH security option. This option must be enabled in order for you to display specific pages in the Application Server Control Console.
There are three possible workarounds for this problem:
Enable the Allow META REFRESH option for all pages you display in Internet Explorer:
Select Internet Options from the Internet Explorer Tools menu.
Click the Security tab.
Click Custom Level.
Scroll down to the Miscellaneous options and make sure that the Allow META REFRESH option is enabled.
Use a more specific URL when connecting to the Application Server Control Console.
For example, if you are having trouble accessing http://host:port/, then try entering a more specific URL, such as:
http://host:port/emd/console/
Add the Application Server Control Console URL to the list of Internet Explorer Trusted Sites:
Select Internet Options from the Internet Explorer Tools menu.
Click the Security tab.
Click the Trusted Sites icon, and then click Sites to display the Trusted Sites dialog box.
If you have not enabled Application Server Control security, clear the Require server verification (https:) for all sites in this zone check box.
Enter the URL for the Application Server Control Console and click Add.
Before you can perform backup and recovery operations from the Application Server Control Console on Windows, you must verify that the System user account is a member of the ORA_DBA user group.
For example, on Windows 2000 Professional or Windows XP systems:
Right-click My Computer and select Manage.
Select Local Users and Groups and then open the Groups folder.
Double click the ORA_DBA group and verify that "NT AUTHORITY\SYSTEM" is a member of the group.
If it is not in the list, click Add to add the NT AUTHORITY\SYSTEM user to the ORA_DBA group.
During installation of J2EE, Oracle Business Intelligence, Portal and Wireless, and Enterprise Manager Agent and Console, some of the errors that show up in the log files are harmless and can be ignored. These errors may come up in the emias.log, em-application.log, and emagent.trc files.
Some of these errors are listed the following examples:
Example 20-2 Error in emias.log file
ERROR cache.CacheManager run.519 - Exception message: sleep interrupted java.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at oracle.sysman.emSDK.svc.cache.CacheManager$Checker.run(CacheManager.java:507) at java.lang.Thread.run(Thread.java:534)
Example 20-3 Error in emias.log file
2005-07-01 16:20:23,231 [EMUI_16_20_23_/console/metrics/metricData] ERROR metrics.AllMetricsUtil getNLSString.126 - Can't find resource for bundle oracle.sysman.eml.rsc.gen.hostMsg, key host_paging_activity_pgactive java.util.MissingResourceException: Can't find resource for bundle oracle.sysman.eml.rsc.gen.hostMsg, key host_paging_activity_pgactive at java.util.ResourceBundle.getObject(ResourceBundle.java:326) at java.util.ResourceBundle.getObject(ResourceBundle.java:323) at java.util.ResourceBundle.getString(ResourceBundle.java:286) at oracle.sysman.ias.sta.metrics.AllMetricsUtil.getNLSString(AllMetricsUtil.java:122) at oracle.sysman.ias.sta.metrics.MetricData.getMetricData(MetricData.java:389) at oracle.sysman.ias.sta.metrics.MetricData.getHeader(MetricData.java:194) at oracle.sysman.ias.sta.metrics.MetricCtlr.prepareData(MetricCtlr.java:118) at oracle.sysman.emSDK.svlt.PageHandler.handleRequest(PageHandler.java:419) at oracle.sysman.emSDK.svlt.EMServlet.myDoGet(EMServlet.java:728) at oracle.sysman.emSDK.svlt.EMServlet.doGet(EMServlet.java:307) at oracle.sysman.eml.app.Console.doGet(Console.java:271) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:837) at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330) at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285) at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126) at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) at java.lang.Thread.run(Thread.java:534)
Example 20-4 Error in em-application.log
05/07/01 02:23:03 emd: Portal Configuration Interface failed to initialise: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 6 at java.util.Vector.remove(Vector.java:792) at oracle.ias.sysmgmt.context.RequestContext.removeLastEntry(Unknown Source) at oracle.ias.sysmgmt.instrumentation.Timer.stop(Unknown Source) at oracle.ias.sysmgmt.clientmetadata.MetadataAccessHelper.<init>(Unknown Source) at oracle.ias.sysmgmt.clientmetadata.MetadataAccessImpl.<init>(Unknown Source) at oracle.ias.sysmgmt.clientmetadata.MetadataAccessFactory.getInstance(Unknown Source) at oracle.ias.sysmgmt.smi.SMIEntryPoint.<init>(Unknown Source) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274) at oracle.ias.sysmgmt.smiapi.SMISessionManager.loadAndCreateInstance(Unknown Source) at oracle.ias.sysmgmt.smiapi.SMISessionManager.createSession(Unknown Source) at oracle.ias.sysmgmt.EntryPoint.getConfiguration(Unknown Source) at oracle.webdb.config.smi.GeneralConfig.initialiseEnviroment(Unknown Source) at oracle.webdb.config.smi.CacheConfig9025Imp.read(Unknown Source) at oracle.webdb.config.smi.CacheConfigLatestImp.read(Unknown Source) at oracle.webdb.monitoring.hawkeye.PortalIntegration$InitThread.run(Unknown Source)
Example 20-5 Error in emagent.trc after securing Enterprise Manager Agent and Console
2005-07-01 17:27:51 Thread-1505459120 WARN ssl: fd=20, nmehlssl_write nzos_Write error = 28862 2005-07-01 17:29:38 Thread-965684144 WARN ssl: fd=17, nmehlssl_write nzos_Write error = 28862 2005-07-01 17:32:35 Thread-965684144 WARN ssl: fd=19, nmehlssl_write nzos_Write error = 28862 2005-07-01 17:38:35 Thread-965684144 WARN ssl: fd=19, nmehlssl_write nzos_Write error = 28862 2005-07-01 17:42:37 Thread-965684144 WARN ssl: fd=19, nmehlssl_write nzos_Write error = 28862 2005-07-01 17:48:34 Thread-1235123120 WARN ssl: fd=18, nmehlssl_write nzos_Write error = 28862 2005-07-01 17:53:34 Thread-965684144 WARN ssl: fd=19, nmehlssl_write nzos_Write error = 28862
This section describes documentation errata. It includes the following topic:
Section 20.2.1, "Online Help for the Application Server Control All Metrics Page"
Section 20.2.2, "Error in Online Help Topic About Regular Expressions"
Most of the component home pages within the Application Server Control include an All Metrics link. When you click this link, Enterprise Manager displays the All Metrics page, which provides a comprehensive list of all the performance metrics you can monitor for the selected component.
In most cases, you can click a metric name on the All Metrics page to display the Metric Details page, and then click Help to get more information about the selected metric.
However, for some metrics, clicking Help will display a Topic not found error. This problem will be addressed in a future version of Oracle Application Server.
In other cases, the online help provided for a particular metric might refer to features available only when you are centrally managing your application server instance with the Grid Control Console. For example, the online help might refer to thresholds, alerts, or the display of historical data about a metric. In those cases, you can access these additional monitoring features by installing and configuring Grid Control Console.
In the Application Server Control online help topic "About Regular Expressions," the example for the asterisk (*) character shows:
OC4J*
The example should instead show the following:
OC4J.*
Section 21.1.19, "Restrictions When Specifying Remote Directories for Backup and Recovery Configuration Settings in the Application Server Control Console Console" has been removed from chapter 21 Oracle Enterprise Manager of Oracle Application Server Release Notes for Microsoft Windows (64 Bit) on Intel Itanium. This issue is related to the Standard Edition One release of Oracle Application Server, and therefore, it does not apply to Oracle Application Server for Microsoft Windows (64 Bit) on Intel Itanium because this is the first full release for this platform.
