Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for hp-ux Itanium and Linux Itanium
B15871-05
  Go To Documentation Library
Home
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

9 Oracle Enterprise Manager

This chapter describes issues with Oracle Enterprise Manager. It includes the following topics:

9.1 General Issues and Workarounds

This section describes general issues and their workarounds for Oracle Enterprise Manager Application Server Control. It includes the following topics:

9.1.1 Setting Globalization Support and Operating System Locale Environment Variables

If you launch a command line tool such as emctl in a non-English setup environment to start a process, then ensure the operating system locale and the 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 Central Console installations.

If these environment variables are not set prior to Oracle Application Server or Central Console installations, then non-ASCII characters will appear incorrectly in Application Server Control or Central Console, respectively. To prevent this problem from occurring, set these two environment variables prior to installation. If you cannot set the environment variables prior to installation, then 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 the environment variables:

9.1.1.1 Checking the Operating System Locale

Ensure that the LC_ALL or LANG environment variables are set with the appropriate value. To check the current setting, issue the following command:


$PROMPT> locale 

9.1.1.2 Setting the Operating System Locale

If you are using bash or zsh, then to set the locale environment variable of the operating system, issue the export command. For example:


export LANG=zh_CN



In this example, the variable is being set to Simplified Chinese. For the specific value in each operating system, refer to the documentation specific to the operating system.

If you are using csh or tcsh, then issue the setenv command:


setenv LANG zh_CN

9.1.1.3 Checking the NLS_LANG Environment Variable

Ensure that the NLS_LANG environment variable is set to an appropriate and compatible value with the operating system locale setting. In addition, ensure that the Grid Control Management Repository database character is set if Grid Control is being used to centrally manage the Oracle Application Server. For the specific value of the language or the character set, refer to the Globalization Support Guide of the Oracle product you are using.

If the platform is a Windows-based operating system, then the default NLS_LANG setting in the registry should be used as is. In addition, check to see if the NLS_LANG setting exists in $ORACLE_HOME/opmn/conf/opmn.xml on UNIX or ORACLE_HOME\opmn\conf\opmn.xml on Windows. 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, then ensure that the NLS_LANG setting in the opmn.xml file is identical to the NLS_LANG environment variable.

9.1.1.4 Setting the NLS_LANG Environment Variable

If you are using bash or zsh, then to set the NLS_LANG environment variable, issue the export command. For example:


export NLS_LANG="Simplified Chinese_China.ZHS16GBK"



In this example, the variable is set to Simplified Chinese. For the specific value in each operating system, refer to documentation specific to the operating system.

If you are using csh or tcsh, then issue the setenv command. For example:


setenv NLS_LANG "Simplified Chinese_China.ZHS16GBK" 

9.1.2 Timestamp on Log Files May Not Be Accurate

The log file timestamps shown by the operating system which are displayed in Log Viewer of the Application Server Control are not always correct. The log file may contain recent log messages but the timestamp available from operating system is normally older than the last message written to the file.

9.1.3 Errors When Configuring Components or Adding or Removing OC4J Instances

While installing Oracle Management Agent 10.1.0.2 on a computer which has one or more instances of Oracle Application Server 10g (10.1.2), you may encounter errors in Application Server Control if you modify your component configuration. 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 work around this problem, install Oracle Management Agent 10.1.0.3 or later patchsets.

9.1.4 Problems with the Progress Page When Using a Macintosh Browser

When you perform an operation with Application Server Control, such as creating a OC4J instance, Enterprise Manager displays a progress page that 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 is not displayed.

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 10g Administrator's Guide for more information about using the EM_OC4J_OPTS environment variable

9.1.5 Error when Clicking Topology Link from Host Page

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.

9.1.6 Error when using the ADF BUSINESS COMPONENT Link on the Host 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.

9.1.7 Posting Data From the Logging Pages

After you configure security for 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 regarding 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 work around this problem, download the Microsoft Q831167.exe package and any other recommended related patch recommend by Microsoft.

9.1.8 Additional Step when Removing an Application Server Target from the Central Console

If an Oracle Application Server 10g (9.0.4) or 10g Release 2 (10.1.2) target is removed from the Central Console, the Infrastructure page in the Application Server Control will still show Central Management as Configured.

To reset the Central Management section of the page, delete the following file from centralagents.lst in the application server Oracle home:

  • In UNIX, $ORACLE_HOME/sysman/emd/centralagents.lst

  • In Windows ORACLE_HOME\sysman\emd\centralagents.lst (Windows)

9.1.9 Grid Control Agent 10.1.0.3

Oracle does not support Grid Control Agent (10.1.0.3) running on HP-UX Itanium or Linux Itanium monitoring an Application Server 10g Release 2 (10.1.2).

9.1.10 Security Considerations When Changing Schema Passwords with the Application Server Control

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 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 10g Administrator's Guide for more information about the benefits of configuring security for the Application Server Control

To avoid these potential security issues, perform the following procedure before changing a schema password in the Application Server Control Console:

  1. Stop the Application Server Control.

    You can stop the Application Server Control by entering the following command in the Application Server Control Oracle home:

    
    ORACLE_HOME/bin/emctl stop iasconsole
    
    
    
    

    See Also:

    The "Starting and Stopping" chapter of the Oracle Application Server 10g Administrator's Guide

  2. Secure the Application Server Control by entering the following command:

    
    ORACLE_HOME/bin/emctl secure iasconsole
    
    
    
    \bin\emctl secure iasconsole
    
    

    See Also:

    "Configuring Security for Enterprise Manager Application Server Control Console" in Appendix A of the Oracle Application Server 10g Administrator's Guide

  3. 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
    
    
    
    
  4. 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" />
    
    
    
    
  5. 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"/>
    
    
    
    
  6. Save and close the emd-web-site.xml file.

  7. Start the Application Server Control.

    You can start the Application Server Control by entering the following command in the Application Server Control Oracle home:

    
    ORACLE_HOME/bin/emctl start iasconsole
    
    
    
    

    See Also:

    The "Starting and Stopping" chapter of the Oracle Application Server 10g Administrator's Guide

9.1.11 Problems Viewing OracleAS Portal Metrics When OracleAS Portal is Configured for Secure Sockets Layer (SSL)

When you use Application Server Control to monitor an instance of 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:

  1. Obtain the Certificate of the Web Site's Certificate Authority, as follows:

    1. In Microsoft Internet Explorer, connect to the HTTPS URL of the application server you are attempting to monitor.

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

    3. Click the Certificate Path tab and select the first entry in the list of certificates.

    4. Click View Certificate to display a second Certificate dialog box.

    5. Click the Details tab on the Certificate window.

    6. Click Copy to File to display the Certificate Manager Export wizard.

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

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

  2. Update the list of Certificate Authorities, as follows:

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

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

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

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

    
    /dua0/oracle/portal_certificate.cer
    
    
    
    
  5. 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.

Example 9-1 Example Content of an Exported Certificate


-----BEGIN CERTIFICATE-----

MIIDBzCCAnCgAwIBAgIQTs4NcImNY3JAs5edi/5RkTANBgk

... base64 certificate content ...

------END CERTIFICATE------

9.1.12 Database Management in OracleAS Cold Failover Cluster (Infrastructure) Configurations

In both non-distributed and distributed OracleAS Cold Failover Cluster (Infrastructure) configurations, you can run the Database Console only from the node where you installed the OracleAS Metadata Repository. For example, if your hardware cluster consists of node A and node B, and you performed the installation from node A, then you can only run the Database Console from node A. The reason for this is that the Database Console uses the physical hostname instead of the virtual hostname.

If node A fails, you will not be able to run Database Console from node B. To manage the OracleAS Metadata Repository database from node B, you have to use other tools, such as SQL*Plus.

9.2 Documentation Errata

This section describes documentation errata. It includes the following topics:

9.2.1 Online Help for the Application Server Control All Metrics Page

Most of the component home pages within 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 some 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 the rest of the 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 Central 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 Central Console.

9.2.2 Error in Online Help Topic About Regular Expressions

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