Oracle Support Master Note for 10g Grid Console Browser / User-interface Issues

For most current information refer Master Note for 10g Grid Console Browser / User-interface Issues (Doc ID 1190323.1)

 

 

Master Note for 10g Grid Console Browser / User-interface Issues (Doc ID 1190323.1)

 

In this Document
  Purpose
  Scope and Application
  Master Note for 10g Grid Console Browser / User-interface Issues
     Grid Console User-interface Concepts
     Diagnostic Tools Available for Troubleshooting Grid Console User-interface Issues
     Troubleshooting Grid Console Browser / User-Interface Issues
     Best Practices (Certification, Maintenance Activities, OCM, Healthcheck, CPU & PSU)
  References


Applies to:

Enterprise Manager Grid Control - Version: 10.1.0.2 to 10.2.0.5 - Release: 10.1 to 10.2
Information in this document applies to any platform.

Purpose

This Master Note helps understand Grid Console Browser / User-Interface Issues and provides assistance in using diagnostics effectively to debug/troubleshoot and resolve issues encountered.

Scope and Application

This document is intended to assist Enterprise Manager Grid Control Administrators effectively troubleshoot Grid Console Browser / User-interface Issues. This document covers the following topics:

1. Grid Console User-interface Concepts.
2. Diagnostic Tools Available for Troubleshooting Grid Console User-interface Issues.
3. Troubleshooting Console Browser / User-Interface Issues.
4. Best Practices (Maintenance Activities, OCM, Healthcheck, CPU & PSU and Certification).

Master Note for 10g Grid Console Browser / User-interface Issues

Grid Console User-interface Concepts

The Grid Console, also known as Grid Control Console / Enterprise Manager (EM) Console is the user / web-based interface to the Grid Control setup. From the Grid Console, you can monitor and administer your entire computing environment from one location on the network. All the services within your enterprise, including hosts, databases, listeners, application servers, and so on, are easily managed from one central location. Thus, you can access the Grid Control setup from any client machine which has a web-browser installed, provided that the communication channels to the OMS machine is open.
The 10g Grid Console uses the default OracleAS Web Cache port (for example, port 7777 on UNIX systems and port 80 on Windows systems) to connect to the Oracle HTTP Server component of the OMS. The connection can be via http / https. For example:

http://omsmachine.domain:7777/em
https://omsmachine.domain:4444/em

If the communication is successful, then the above URL will show a login page where details of a valid Enterprise Manager Administrator and password can be entered.

For additional details, refer to:

  • List of Supported browsers

    Note 412431.1: Oracle Enterprise Manager Grid Control Certification Checker
    Section: Browser Certifications
  • Identifying the Console URL

    Note 392979.1: How to Identify the URL to login to the 10g Enterprise Manager Grid Console
    Note 763844.1: How to Verify the Hostname/IP Address Resolution Between the 10g Enterprise Manager Grid Control Components?
  • Language and Timezone in the UI pages

    Note 413864.1: Grid Control UI: How to Choose / Modify the Enterprise Manager Grid Console Language?
    Note 338481.1: Grid Control UI: How are the Date / Time for the 'Page Refreshed' Value in the Enterprise Manager Pages Computed?
  • Securing and Authenticating access to Grid Console
    • Note 452290.1: How to secure/restrict access to the Enterprise Manager Grid Control console
    • Note 736103.1: How to Configure a Third Party Certificate for HTTPS Access to the Grid Console?
    • Note 1092513.1: Master Note for 10g Enterprise Manager Grid Control Security Framework, Section: Grid Control Components Security Objectives,
      Category area: Grid Control Console Authentication
  • Grid Console Users

    During the OMS installation and configuration, the SYSMAN user (who also owns the repository schema) is created as a super-administrator in the Grid Console. By, default, the SYS / SYSTEM users in the repository database are also configured as Super-Administrators for the Grid Console.
    New administrators can be created as needed from the setup -> Administrators page, after logging into the Console as one of the above users.
    For more details, refer to:
    Note 1092513.1: Master Note for 10g Enterprise Manager Grid Control Security Framework
    Section: Grid Control Components Security Objectives
    Category area: Preferred Credentials and Target Access

    To be able to successfully login to the Grid Console, one must have a valid Enterprise Manager Administrator user name and its password.

Back to Top

  • Modifying the default Session Timeout

    Note 234875.1: How to Change the Default Session Timeout for the 10g Enterprise Manager Grid Console Connections?
  • Adding a custom Logo / Image in the Console

    Note 395029.1: Grid Console UI: How to add a Custom Logo / Banner in the EM Grid Console?

    Note: The steps in the above note should be used to modify the banner in the Grid Console only. Do not modify any other images or gif's similarly, this will affect the normal manner in which the details are displayed in the Grid Console and will not be supported.
  • Enabling Accessibility Mode for users of Assistive technology

    Note 459856.1: Grid Console UI: What Is "Accessibility Mode" and How to Enable / Disable it?
  • Management Packs

    Oracle offers a number of management options, or "Management Packs," that bring together a set of technologies related to a specific area of Enterprise Manager.Each pack has several premium features bundled as part of that pack. Having a pack licensed or unlicensed on a target has a very significant impact on the user experience because the corresponding links, which need the pack, are enabled or disabled accordingly.
  • Abode SVG Viewer / Adobe Flash Player requirement

    Note 562922.1: Grid Console UI: Why is Adobe SVG Viewer / Adobe Flash Player Needed for Grid Console?

Additional Details:

1. In any of the Console pages, clicking on the 'Help' button at the top right-hand corner of the page will launch a help window with context-specific (for the page where the button is clicked) details. You can also click on the 'Search' tab and search for details on a specific topic.

2. Clicking on the 'About Oracle Enterprise Manager' link at the bottom left-hand corner of the page will display the version of the OMS.

3. In 10.2.0.x Grid Control version, clicking on the '+' sign next to 'About Oracle Enterprise Manager' will display the abbreviations for the different Management Packs required for the functionality will be displayed in the UI. Refer to
Note 414671.1: Grid Console UI: How to Display the Management Pack Details for a Particular Functionality in the Grid Control 10gR2 UI?

Back to Top

********************************************************************************

Diagnostic Tools Available for Troubleshooting Grid Console User-interface Issues

  • Extended UI Tracing for Console Operations against Repository Database

    The SQL queries that are being run against the Repository Database, for a console-level activity can be traced using the Extended / SQL Console UI Trace URL:

             http://<omshost>:<port>/em/console/admin/rep/extendedSQLTrace

    The UI tracing is similar to enabling 10046 trace in the repository database for the session from the console. For more details, refer to
    Note 436592.1: Steps to Enable Extended SQL / UI Trace for Enterprise Manager Grid Console Sessions Against Repository Schema
  • 'EM SQL History' for Administrative / Real-time Operations against Target Database

    For many of the Database-related pages in the Grid Console, the data is obtained by making a direct SQL*Net connection from the OMS machine to the target Database. This connection bypasses the Grid Agent on the Database machine; hence it is possible to view certain pages of the database even if the Agent is not running. Such database pages can be classified as:
    • Administrative: Pages which are related to DBA activities against the database, for example: checking the Tablespace information from the Database Administration (till 10.2.0.4 GC) or the Server (from 10.2.0.5 GC) page, adding a datafile, performing a DDL operation against a Table, enabling backup, modifying init.ora parameters etc.
    • Real-time Monitoring: Pages where the real-time information for the Database is shown, for example: the Database Performance page.


For more details on tracing the queries executed by such pages, refer to
Note 357318.1: How to Identify the SQL Used by OMS For Administrative / Real-time Monitoring Pages of a Database Target?

The EMDiagkit is a diagnostic tool developed to assist in diagnosis and correction of Enterprise Manager 10g Framework issues. At present, the tool allows us to extract necessary troubleshooting data from the EM Repository Schema using the repvfy utility.

The details for installation, usage of EMDiagkit are available in

Note 421053.1: EMDiagkit Download and Master Index

  • RDA

    The Remote Diagnostic Agent (RDA) can be executed specifically with the Grid Control / OMS profile name: GridControl and the Database profile name: DB10g / DB11g in order to reduce the number of questions that need to be answered and also to collect all details of the OMS / Database Homes correctly.

    The steps to execute the RDA with GridControl and profiles are explained in:

              
    Note 1057051.1: How to Run the RDA against a Grid Control Installation

    It is highly recommended that the latest EMDiagkit is installed and executed in the OMS home, before running the RDA. This will ensure that the RDA picks up the latest data collected by the EMDiagkit. Any operation performed in the Console will also be logged in the emoms.log / emoms.trc of the OMS. Enabling DEBUG level trace and reproducing the issue can provide more details about the Console thread, performing the operations.

Back to Top

********************************************************************************

Troubleshooting Grid Console Browser / User-Interface Issues

Accessibility and performance of the Grid Console UI pages, to a very large extent, depend on the performance of the OMS and Repository components. Hence, before troubleshooting any problems related to the Grid Console UI, the following should be verified:

1. Is the OMS up and running?

       cd <OMS_HOME>/bin
       emctl status oms

2. Is it possible to resolve the hostname / IP address of the OMS machine, from the machine where the Grid Console is being accessed?
Refer to
Note 763844.1: How to Verify the Hostname/IP Address Resolution Between the 10g Enterprise Manager Grid Control Components?

3. If the OMS is behind a firewall, is the OMS HTTP Server port open in the firewall for communication to succeed? Refer to
Note 1088393.1: How to Verify the Communication Between the 10g Enterprise Manager Grid Control Components via Firewall/Proxy?

4. If the security settings in the browser is restrictive, then trying to access the Grid console can result in a blank page. Verify the security settings, if necessary with the help of your System Administrator, and modify them so that there is unrestricted communication to the OMS.
Example:
Note 365102.1: Accessing the 10g Enterprise Manager Grid Console URL Returns a Blank Page Without Login Screen / Errors

5. To verify if the problem is specific to a particular machine / browser, try to access the Grid Console URL from another machine / browser.

6. If you get an "Internal Error has occurred. Check the log file for details" on any Grid Console page, it actually indicates a problem with the OMS or the code used in that console page for a particular operation. Checking the <OMS_HOME>/sysman/log/emoms.trc will provide more errors regarding the Console.
For understanding the entries in the OMS trace files, refer to the details in
Note 1098262.1: Master Note for Diagnostic Tools for 10g Enterprise Manager Grid Control Components, Section: Diagnostic Tools for the 10g Oracle Management Service (OMS),
Topic : OMS Log/Trace Files

7. Depending on the privileges / roles assigned to the Administrator who is logging into the Grid Console, certain Console pages / targets / features may not be accessible. For details on the privileges / roles, refer to
Oracle Enterprise Manager Administration 10g Release 5 (10.2.0.5),
Chapter 3 Enterprise Manager Security,
Topic :
Privileges and Roles

Some more problems and troubleshooting steps are listed below:

  • Communication Failure between the Grid Console and OMS

    Incorrect communication setup between the Grid Console (User Interface) and the OMS can result in the following problems:
    • Trying to access the Grid Console URL from a certified web-browser results in the error:

"page cannot be displayed"

OR

502 Bad Gateway
The following error occurred:

[code=DNS_HOST_NOT_FOUND] The host name was not found during DNS lookup. Contact your system administrator if the problem is not found by retrying the URL.

 

    • Trying to access the Grid console using unsecured URL (using http) fails with:

Forbidden
You don't have permission to access /em/console/home on this server.
-----------------------------------------------
Oracle-Application-Server-10g/10.1.2.2.0 Oracle-HTTP-Server Server at omsmachine.domain: 7778


But access to the secured URL (using https) works fine.


  • For troubleshooting steps, refer to
    Note 1089443.1: How to Troubleshoot Communication Between the Grid Console (UI) and Oracle Management Service (OMS) Components in 10g Enterprise Manager Grid Control

    To find documents related to communication problems between the Grid Console (UI) and OMS, login to My Oracle Support portal and query the 'Knowledge' with the following keywords:

             Accessing the 10g Grid Console URL Results <actual error message seen>

    Some examples:

            Accessing the 10g Grid Console URL Results in 502 Bad Gateway
           Accessing the 10g Grid Console URL Results in 'page cannot be displayed'
     
  • Slow Console UI Pages
    • If a particular page in the Grid Console is slow, to gather more details refer to the steps in Note 1098262.1:Master Note for Diagnostic Tools for 10g Enterprise Manager Grid Control Components
      Section: Diagnostic Tools for the Enterprise Manager Console Operations
    • To improve the Login performance of the Console Home page, refer to the steps under
      Oracle Enterprise Manager Administration 10g Release 5 (10.2.0.5),
      Chapter 12 - Maintaining and Troubleshooting the Management Repository,
      Improving the Login Performance of the Console Home Page

Some examples:

Note 836290.1: Grid Control Performance: OMS Crashes When Running Customized Report with 'CHART FROM SQL' Element in Console
Note 781347.1: Grid Control Performance: OMS Crashes With 'OutOfMemory' Errors When Editing / Configuring a Group
Note 436690.1: Grid Console Performance: Pages in Console are Slow and Sometimes Return Timeout

  • Login Failures

    Login to the Grid Console may fail errors such as:

Login operation failed.

OR

Your username and/or password are invalid.

OR

This user is not a valid Enterprise Manager Administrator

OR

Authentication failed. Verify username/password that you have provided. If you believe you entered correct credentials, your account may have been locked, contact system administrator to unlock your account. (From 10.2.0.5 OMS version only)


The Login failures can occur it the

    • Username entered is not a valid Enterprise Manager Administrator
    • Password for the Administrator is entered wrongly.
    • Administrator account has been locked at the Repository Database level.
    • Administrator account has been disabled from logging into the Grid Console, etc.


To find documents related to communication problems between the Grid Console (UI) and OMS, login to My Oracle Support portal and query the 'Knowledge' with the following keywords:

          Logging into the 10g Grid Console URL Results <actual error message seen>

Some known issues:

Note 784532.1: Logging into the 10g Grid Console URL Results in "Login Operation Failed"
Note 455165.1: Logging into the 10g Grid Console URL Results in "This user is not a valid Enterprise Manager Administrator"

  • Certificate Errors when Accessing HTTPS Grid Console URL

    When the OMS is secured, the SSL certificates are self-generated (signed by Oracle Certificate Authority), by default, and not signed by any third party Certificate Authority. If this certificate is not imported in the Trusted Root Certification Authorities store of the browser, then 'Certificate Errors' will be seen when accessing the HTTPS Grid Console URL from a browser.

    Steps for importing the certificate in an Internet Explorer browser are described in
    Note 437660.1: Enterprise Manager Console UI: Accessing the Grid Console / DBConsole / Metric Browser shows "Certificate Errors".

    Note:
    Third-party Certificates can be used from 10.2.0.5 Grid Control version onwards. Refer to
    Note 736103.1: How to Configure a Third Party Certificate for HTTPS Access to the Grid Console?
  • Language or Timezone issues

    The Language, timestamp / timezone details and format shown in the Grid Console pages depend on multiple formats:
    • Language settings chosen in the browser in which the Grid Console is being accessed.
    • Language that has been chosen when installing the Grid Control software.
    • Font files that have been installed in the OMS home, for the language chosen at the time of installation.
    • The Timezone value using which the OMS has been started up.
    • Timezone value using which the Agents on the Target machines have been started up.
    • Incorrect calculation between the OMS machine timestamp / timezone and the target machine timestamp / timezone, for computing the timestamp in the Target related pages (these would be code defects in the product).


Some known issues:

Note 340952.1 Enterprise Manager Console UI: Cannot view Chinese / Japanese (Asian) Characters on the Buttons of Enterprise Manager Console
Note 968704.1: Grid Console UI: Grid Console UI: 'Page Refreshed' / 'Latest Data Collected' Timestamp in the Console Pages Does not Include AM / PM

To find documents related to timezone issues in the Grid Console, login to My Oracle Support portal and query the 'Knowledge' with the following keywords:

    Grid Console UI: 'Page Refreshed'
   
OR Grid Console UI:  'Latest Data Collected From Target'

Some examples:

Note 959775.1: Grid Console UI: 'Latest Data Collected From Target' on Host Performance Page shows Time of Target Machine but Timezone of Repository
Note 829751.1: Grid Console UI: Timezone in the 'Page Refreshed' Value is Shown as GMT Rather than Local Timezone of the OMS

  • Searching My Oracle Support Documents for Grid Console User-Interface Issues

    As the search is specific to Enterprise Manager Grid Control issues, we recommend that the search be performed only under the Grid Control section, using the following navigation:

    Login to My Oracle Support then Click Knowledge -> Enterprise Management -> Enterprise Manager Consoles - Packs - and Plugins -> Enterprise Manager Grid Control ->All of Enterprise Manager Grid Control.
  • Using RDA and EMDiagkit for troubleshooting User-Interface Issues
    • The RDA output generated with the GridControl profile is very useful in obtaining all the configuration files and log/trace files together. These can assist in identifying if a problem is specific to the Console UI or other components like the OMS / Repository.
    •  The EMDiagkit output is very useful in diagnosing problems / mis-configurations with Grid Control Repository objects, which can result in errors when accessing the Grid Console URL.


Note: It is highly recommended that the latest EMDiagkit is installed and executed in the OMS home, before running the RDA. This will ensure that the RDA picks up the latest data collected by the EMDiagkit.

Back to Top


********************************************************************************

Best Practices (Certification, Maintenance Activities, OCM, Healthcheck, CPU & PSU)

This section lists some of the best practices which will help prevent problems with Grid Console Browser / User-interface Issues.

EM Certification Checker

It is strongly recommended that you always use a certified combination of OMS, Agent and Repository Database for managing Targets which are certified with this combination.
The Enterprise Manager certification details are available in:

Note 412431.1: Oracle Enterprise Manager 10g Grid Control Certification Checker

Maintenance Activities

  • Enable Log Rotation for the access_log and error_log files created by the httpd_em.conf file:
    Note 436690.1: Grid Console Performance: Pages in Console are Slow and Sometimes Return Timeout
  • Do not use the browser 'Back' button to navigate to the earlier seen pages in the Grid Console. Most pages do not support this action and may result in errors or inconsistent data.
  • Execute EMDiagKit at regular intervals (once per week or more frequently, depending on your setup) and check for any new problems that are reported for the OMS / Repository operations.
  • Take valid backups of the Agent, OMS and Repository Database Homes at regular intervals, to restore back any configuration files that are deleted by accident.
    For a 10.2.0.5 OMS, the 'emctl exportconfig oms' command can be used to backup the necessary OMS configuration details. Refer to the details in Oracle Enterprise Manager Administration 10g Release 5 (10.2.0.5), Chapter - 9 Backup, Recovery, and Disaster Recovery. Topic :
    OMS Backup and Recovery.

Back to Top


OCM

Oracle Configuration Manager (OCM) works with My Oracle Support to enable proactive support capability that helps you organize, collect and manage your Oracle configurations by providing Proactive configuration-specific notification of Security and General Alerts, HealthCheck recommendations based on Support Best practices when using configuration auto-collection, Simplified Service Request logging, tracking and reporting and Project cataloging of key milestones and contacts associated with your configurations.

  • Among these the following topics are related to the Enterprise Manager Components:
    • 2.52 Oracle Enterprise Manager 10g Grid Control Management Agent:
    • 2.54 Oracle Enterprise Manager 10g Grid Control Management Service
    • 2.53 Oracle Enterprise Manager 10g Grid Control Management Repository
    • 2.72 Oracle Grid Control Repository (for oracle_emrep target)
    • 2.38 Oracle Agent Deployment Configuration (oracle_emd target)
    • 2.73 Oracle Home
    • 2.23 Host

Note: The above list is expected to be expanded as and when new collections are introduced in future.

  • It is also advisable to review the collections available for the Database instance, so that the Database hosting the repository can be monitored as well:
    • 2.10 Database Instance
    • 2.78 Oracle Listener

Healthcheck

Healthchecks are executed dynamically against the Oracle Configuration Manager uploaded configurations in My Oracle Support. These checks, based on Oracle Best practices, will proactively notify you of potential problems in your environment, and provide recommendations that help you improve system performance and avoid problems in your Oracle environment.

  • If you are receiving any Healthcheck alerts in My Oracle support, then refer to the following document for the alert details and its corresponding document for resolving the same:

Note 868955.1: My Oracle Support Health Checks Catalog

  • For Healthchecks specific to the Enterprise Manager and Repository Database, refer to the sections titled:
    • Enterprise Manager (for the OMS)
    • Oracle Database (for the Database hosting the Repository)

Back to Top


CPU and PSU

  • CPU

    Critical Patch Updates (CPU) is the primary means of releasing security fixes for Oracle products. They are released on the Tuesday closest to the 15th day of January, April, July and October. This
    page lists all the currently available Critical Patch Updates (CPUs) in chronological order and is updated whenever new Critical Patch is released. You can also subscribe to the CPU Email Alerts using the steps listed here.

    To obtain the latest CPU patch details for the Enterprise Manager Grid Control and its dependent products - Oracle Application Server and Oracle Database:

    - In the
    page, click on the link shown for the latest CPU in the table under the 'Critical Patch Updates'.
    - The next page, lists all the products which have security fixes in the chosen CPU release. Scroll down to 'Patch Availability Table ..' topic and find the table with details for the Product Group and Patch Availability and Installation Information.
    - In the table, find the row related to Product Group: 'Oracle Enterprise Manager' and pick up the document number given in the Patch Availability and Installation Information column. In the document, navigate to:

                 "Critical Patch Update Availability for Oracle Products" and then to
                 "Oracle Enterprise Manager Grid Control"
  • PSU

    Patch Set Updates (PSU) are proactive cumulative patches containing recommended bug fixes that are released on a regular and predictable schedule. PSUs are on the same quarterly schedule as the Critical Patch Updates (CPU), specifically the Tuesday closest to the 15th of January, April, July, and October. The PSUs serve as a new baseline version for reporting issues to Oracle, hence it is always recommended to be on the latest PSU release.
    • For more details on PSU, refer Note 854428.1: Patch Set Updates for Oracle Products
    • For Enterprise Manager specific PSU, refer Note 822485.1: Oracle Recommended Patches -- Oracle Enterprise Manager
  • Choosing between CPU / PSU patches

    The PSU and CPU released each quarter contain the same security content. However, the patches employ different patching mechanisms, so customers need to choose wisely which patch satisfies their needs better:
    • A PSU can be applied on the CPU released at the same time or on an any earlier CPU for the base release version. A PSU can be applied on any earlier PSU or the base release version. CPUs are only created on the base release version. 
    • Once a PSU has been installed, the recommended way to get future security content is to apply subsequent PSUs. Reverting from PSU back to CPU, while possible, would require significant effort, and so is not advised.
  • Getting CPU / PSU patch recommendations via OCM

    OCM also collects and recommends the latest CPU and PSU patch that can be applied to a particular Oracle Home. These details can be seen in the My Oracle Support ->Patches and Updates -> Patch Recommendations section
    - 'Security' patch recommendations include the CPU patches.
    - 'Other Recommendations' include the PSU patches.

Back to Top

References

NOTE:1081865.1 - Master Note for 10g Grid Control OMS Process Control (Start, Stop and Status) & Configuration
NOTE:1082009.1 - Master Note for 10g Grid Control Agent Process Control (Start, Stop & Status) & Configuration
NOTE:1086343.1 - Master Note for 10g Grid Control Enterprise Manager Communication and Upload issues
NOTE:1087997.1 - Master Note for 10g Enterprise Manager Grid Control Agent Performance & Core Dump issues
NOTE:1092513.1 - Master Note for 10g Enterprise Manager Grid Control Security Framework
NOTE:1098262.1 - Master Note for Diagnostic Tools for 10g Enterprise Manager Grid Control Components
NOTE:1161003.1 - Master Note for 10g Grid Control OMS Performance Issues

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

News and Troubleshooting tips for Oracle Database and Enterprise Manager

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today