Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-1662439.1
Update Date:2017-10-31
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1662439.1 :   Master Note On Exalytics Instrumentation And Diagnostics - Use To Diagnose and Troubleshoot Problems on Exalytics  


Related Items
  • Hyperion Essbase
  •  
  • Business Intelligence Suite Enterprise Edition
  •  
  • Linux OS
  •  
  • Oracle Exalytics Software
  •  
  • Oracle TimesTen In-Memory Database
  •  
  • Exalytics In-Memory Machine X2-4
  •  
  • Exalytics In-Memory Machine X3-4
  •  
Related Categories
  • PLA-Support>Eng Systems>Exalytics>Oracle Exalytics>DB: Exalytics_EST
  •  




In this Document
Purpose
Details
 What is meant by "Instrumentation" or "Diagnostics"
 Hardware Instrumentation and Diagnostics
 Auto Service request (ASR) -  use to monitor hardware and components and automatically open Support Request (SR) when errors detected
 ASRExacheck - use to validate communication between Exa* nodes and ASR Manager
 Exalytics Diagnostics - use to collect disk sub-system information when disk error suspected
 ILOM Snapshot - use to collect service processor diagnostic data for failing/failed hardware components (dimm, processor, fan, power supply, etc.)
 Linux Operating System and Oracle Virtual Machine (OVM)
 OSWatcher - use to collect operating system and network metrics for Linux performance issues
 Sosreport - use to collect operating system data including network configuration and logs for Linux OS issues
 VMPinfo3 - use to gather messages, logs and other data for Exalytics OVM environments
 Software Applications
 Remote Diagnostic Agent (RDA) - use to collect product versions, log files and configuration for OBIEE and TimesTen on Exalytics
 OBIEE Diagnostics - use to collect configuration, log and debug information for OBIEE problems on Exalytics
 Enterprise Performance Management (EPM) and Essbase - use to collect and validate configuration and logs for Essbase and EPM problems on Exalytics
 Times Ten
References


Applies to:

Business Intelligence Suite Enterprise Edition - Version 11.1.1.6.0 to 12.2.1.3.0 [Release 11g to 12g]
Linux OS - Version Oracle Linux 5.5 with Unbreakable Enterprise Kernel [2.6.32] and later
Oracle TimesTen In-Memory Database - Version 11.2.2.2.0 and later
Oracle Exalytics Software - Version 1.0.0.0.0 to 2.0.0.1.0 [Release 1.0 to 2.0]
Exalytics In-Memory Machine X2-4 - Version All Versions and later
Information in this document applies to any platform.
Checked for currency 29-DEC-2015.

Purpose

 This is a master note on Exalytics Instrumentation / diagnostics utilities.

Details

What is meant by "Instrumentation" or "Diagnostics"

The terms "Instrumentation" and "Diagnostics" are used interchangeably and refer to tools that help collect, inform, diagnose, or troubleshoot.  These features can be used by Oracle customers and Oracle Support to diagnose product and hardware problems.

The following Exalytics Instrumentation/ Diagnostics tools and their suggested use cases are available:

  • Auto Service Request (ASR) - use to identify hardware and component errors pro-actively and automatically opens a Support Service Request (SR)
  • ASRExacheck- use to validate communication between Exa* nodes and ASR Manager
  • Exalytics Diagnostics Script -  use to collect disk sub-system information when disk error suspected
  • ILOM Snapshot - use to collect service processor diagnostic data for failing/failed hardware components (dimm, processor, fan, power supply, etc.)
  • OS Watcher - use to collect operating system and network metrics for Linux performance issues
  • Remote Diagnostic Agent (RDA) -use to collect product versions, log files and configuration for OBIEE and TimesTen on Exalytics
  • Sosreport - use to collect operating system data including network configuration and logs for Linux OS issues
  • VMPinfo3 - use to gather messages, logs and other data for Exalytics Oracle Virtual Machine (OVM) environments
  • OBIEE Security Diagnostics - use to troubleshoot security and authentication errors in OBIEE on Exalytics
  • OBIEE Logging - use to collect logs for specific OBIEE errors
  • OBIEE Core Dump and Stack Trace - use to debug OBIEE core dumps on Exalytics
  • EPM Deployment Report - use to validate and list EPM components after installation
  • Essbase Agent Hangs - use to troubleshoot Essbase Agent hangs on Exalytics
  • Essbase XCP Files - use to gather log/error details for Essbase problems
  • TimesTen

Hardware Instrumentation and Diagnostics

Auto Service request (ASR) -  use to monitor hardware and components and automatically open Support Request (SR) when errors detected

Oracle Auto Service Request (ASR) is a feature of Oracle Premier Support for Systems and Oracle/Sun Limited Warranty that is designed to automatically request Oracle service when specific hardware faults occur. ASR is designed to enable faster problem resolution by eliminating the need to initiate contact with Oracle services for hardware failures, reducing both the number of phone calls needed and overall phone time required.

For more information on ASR refer to following documentation links:

    • How To Obtain And Install Auto Service Request Software (ASR) On An Oracle Exalytics Server <Document 1492709.1>
    • Oracle Auto Service Request (ASR) <Document 1185493.1>
    • Is It Possible To Install Auto Service Request (ASR) On Exalytics OVM Environments <Document 1662861.1>

ASRExacheck - use to validate communication between Exa* nodes and ASR Manager

The ASREXACHECK script is designed to check and test ASR configurations to make sure that the Exa* nodes can communicate to the ASR Manager. This is a non-invasive script that checks configurations only and does not write to any system or configuration files. The asrexacheck script also checks for known configuration issues as well as checking for any previous hardware faults that may not have been reported by ASR due a misconfiguration on the Engineered nodes.

The script can be used on all nodes as well on OEL nodes and Solaris DB Nodes.The Script is now supported on the following platforms of Engineered Systems:

    • Oracle Exalogic Elastic Cloud X2-2, X3-2
    • Oracle Exadata V2, X2-2, X2-8, X3-2, X3-8
    • Oracle Exadata Storage Expansion X2-2, X3-2
    • Oracle Exadata Image version 11.2.0.1.0
    • Oracle Big Data Appliance v1, X3-2
    • Oracle Exalytics In-Memory Machine X2-4

Refer to following MOS Notes for more information on ASREXACHECK

Exalytics Diagnostics - use to collect disk sub-system information when disk error suspected

The Exalytics Diagnostics script (exalyticsdiag.sh) is a diagnostic collection tool for the Oracle Exalytics In-Memory Machine.  It collects various files and outputs from the system and packages them into a tar.bz2 file that can be easily uploaded to a support case to assist the support center in troubleshooting issues.

The script can optionally take two different options to include data collection from the system's Service Processor. The 'ilom' option will collect several outputs from the ipmitool command (see below for a list of the commands) and the 'snapshot' option will collect an ILOM snapshot from the Service Processor.

Refer to following MOS Note for more information on exalyticsdiag.sh:

  • Oracle Exalytics In-Memory Machine diagnostic data collection script <Document 1527167.1>

ILOM Snapshot - use to collect service processor diagnostic data for failing/failed hardware components (dimm, processor, fan, power supply, etc.)

The ILOM snapshot is a tool used to collect diagnostic data on the server processor.  It is useful when encountering problems with warning lights (on the server itself), or hardware errors (in ILOM or other).  The ILOM snapshot can be run via GUI mode in the ILOM console or on the service console itself (via the SP CLI interface).  See the following note for full instructions:

  • SRDC - ES ILOM Snapshot Collection <Document 1674265.1>

Linux Operating System and Oracle Virtual Machine (OVM)

OSWatcher - use to collect operating system and network metrics for Linux performance issues

OS Watcher (OSW) is a collection of UNIX shell scripts intended to collect and archive operating system and network metrics to aid support in diagnosing performance issues.

Refer to following MOS Notes for more information on OSWatcher.

    • Note 301137.1: OSWatcher Black Box User Guide (Includes: [Video])
    • Note 461054.1: OSW System Profile - Sample.
    • Note 580513.1: How To Start OSWatcher Black Box Every System Boot
    • Note 946107.1: What Is The OSWATCHER Black Box Effect On The Server Performance And What Are The Alternative Commands.
    • Note 431069.1: Diagnostic Script to Analyze OSWatcher slabinfo Archives.

Sosreport - use to collect operating system data including network configuration and logs for Linux OS issues

The "sosreport" is a tool to collect troubleshooting data on an Oracle Linux system. It generates a compressed tarball of debugging information that gives an overview of the most important logs and configuration of a Linux system, to be sent to Oracle Support.  The sosreport includes information about the installed rpm versions, syslog, network configuration, mounted filesystems, disk partition details, loaded kernel modules and status of all services.

    • SRDC - Oracle Engineered Systems (ES) Sosreport Data Collection for Linux Servers <Document 1901729.1>

VMPinfo3 - use to gather messages, logs and other data for Exalytics OVM environments

VMPinfo3 is a tool for capturing messages, xend logs, dmesg, ovs-agent logs and other information from Oracle VM 3.x Manager and Servers. It uses the Oracle VM 3.x API to gather information about the current settings of the cluster/Server Pool. The data collected by the vmpinfo includes sosreport from all the Oracle VM Servers managed by the Oracle VM manager system where VMPinfo is being run and Oracle VM Manager log files.

    • <Note 1364933.1> VMPinfo3 Diagnostic Capture for Oracle VM 3 troubleshooting
    • <Note 1521931.1> VMPinfo3 Diagnostic tool for Oracle VM 3.2.1 troubleshooting

Software Applications

Remote Diagnostic Agent (RDA) - use to collect product versions, log files and configuration for OBIEE and TimesTen on Exalytics

Remote Diagnostic Agent (RDA) is a command-line diagnostic tool that is executed by an engine written in the Perl programming language.

Refer to following MOS Note on running RDA on Exalytics:

    • Using Remote Diagnostic Agent (RDA) On An Oracle Exalytics Server <Document 1471566.1>

OBIEE Diagnostics - use to collect configuration, log and debug information for OBIEE problems on Exalytics

    • Core Dumps - see <Note 1382369.1> OBIEE 10g/11g: Steps To Generate Stack Trace (GDB) Output To Debug Core Dump On Linux Operating System
    • General Errors -
      • SRDC - Data Collection for OBIEE 11g Dashboard and Reports Issues <Document 1921068.1>
      • SRDC - Collecting Diagnostic Information for an OBIEE 11g Crash Issue <Document 1905552.1>
      • SRDC - Collecting diagnostic information for an OBIEE 11g MapViewer Issue <Document 1906098.1>
    • BI Security Diagnostics - See "Using BI Security Diagnostics Helper" in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition
      11g Release 1 (11.1.1), Part Number E10543-08

Enterprise Performance Management (EPM) and Essbase - use to collect and validate configuration and logs for Essbase and EPM problems on Exalytics

    • EPM Deployment Report- Topology Report and EPM Deployment History Report -  when search window is display, search on "Generate A Deployment Report"

      • An EPM deployment topology report lists the following information:
        • Logical Web Addresses — all logical Web applications and all Web servers that are configured
        • Application Tier Components — the components configured for each EPM Instance in this deployment, including the Web application URL and domain name for each Web application 
        • Database Connections — all databases configured for EPM System products
        • User Directories — user directories used by EPM System products; configured security providers are listed in the same order as configured in Shared Services
        • Data Directories — data directories used by EPM System products, indicating the directories that need to be on a shared file system

      • EPM Deployment History Report — configuration history of activities on the specified date for each server in the deployment. This report can help you to resolve any issues that might arise in your deployment. For example, you can use the report to verify that there is only one WebLogic domain and that the deployment points to the correct number of database schemas. The deployment report is created from the Shared Services Registry database. You can generate the report from any server in the deployment, and it does require EPM System services to be running.

    • Troubleshooting Essbase Agent Hangs on UNIX Systems <Document 1107095.1>
    • How to Troubleshoot Using the Essbase XCP File <Document 1107112.1>
    • How to Troubleshoot Error, "Unable To Obtain Connection To Hyperion Essbase" <Document 1274650.1>

Times Ten

  • SRDC - Data Collection for TimesTen Errors on Oracle Exalytics Server <Document 1944299.1>
  • SRDC - Data Collection for Exalytics Summary Advisor Issues <Document 1920551.1>




Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback