Data Gathering for Troubleshooting CRS Issues

Applies to:

Oracle Server – Enterprise Edition – Version: 9.2.0.1 to 11.2.0.1.0 – Release: 9.2 to 11.2
Information in this document applies to any platform.
This note includes links to information that will be helpful in providing up from to Oracle Support when logging your TAR. Depending on the type of problem you are having, Oracle Support may require different types of diagnostic information in order to resolve the issue.

Purpose

The information below is not required for logging a TAR however, gathering the information now, or being prepared to gather the information when requested, will help to speed the resolution of your TAR.

File Formats for Data Uploaded to Oracle Support

Oracle Support requests that you upload compressed files (grouped together by node – and labeled as such) in a standard format, such as .tar, .gz, .z or .zip. Uploading files in another, non-standard,  format (such as .rar format) may cause a delay for Oracle Support in assisting you to resolve your problem.

Last Review Date

March 26, 2010

Instructions for the Reader

Troubleshooting Details

Generic Data Gathering for All CRS and RAC Issues

RDA:

Please provide a current RDA from each node in the cluster. Older runs of RDA (i.e. if RDA was run from a previous TAR that was logged a few days or weeks back) will not be able to provide current log information, or performance information, so it is a good idea to have current RDA output from all cluster nodes in a RAC environment.

Information on how to download and run RDA can be found in the following Metalink Note:

Note 314422.1 – Remote Diagnostics Agent (RDA)

For RAC issues, please refer to Note 753489.1

End of Generic Section
=====================================

Data Gathering for Diagnosing CRS Installation Issues

For Diagnosing CRS Installation issues, appropriate data to provide to support includes

CLUVFY Output

Trace output from the Oracle Installer
All Installation Logs

Trace output of root.sh

CLUVFY Output. Please refer to the following note for running the Cluster Verification Utility

Note 339939.1 – Running Cluster Verification Utility to Diagnose Install Problems

Trace Output from Oracle Installer:

On Unix/Linux, launch the installer with tracing turned on i.e.:

On Windows launch the installer using ‘setup.exe’ with:

Logs will be written to the ORACLE_BASE/oraInventory/logs on Unix/Linux

Logs will be written to the ‘C:\Program Files\oracle\Inventory\logs’ on Windows

See also the following Note:

Note 269837.1 – Tracing the OUI from 9.2.0.5 to 10g

All Installation Logs

Logs will be written to the ORACLE_BASE/oraInventory/logs on Unix/Linux

Logs will be written to the ‘C:\Program Files\oracle\Inventory\logs’ on Windows

Please upload all recent/applicable logs from this directory.
Trace output from root.sh

For tracing root.sh, please refer to the following note:

Note 240001.1 – 10g RAC: Troubleshooting CRS Root.sh Problems

End of CRS Install Section
=====================================

Data Gathering for CRS Error/Problems

For troubleshooting CRS errors that are not related to installation, please collect the following information:

Note 272332.1 – CRS 10g Diagnostic Collection Guide

Note 330358.1 – CRS 10g R2 Diagnostic Collection Guide

Please also gather the system messages files from all nodes – depending on your platform, these logs are found in different locations:

End of CRS Error Section
=====================================

Data Gathering for Node Reboots

For troubleshooting of Node Reboots when running Oracle Clusterware, please collect the following information:

Note 272332.1 – CRS 10g R1 Diagnostic Collection Guide

Note 330358.1 – CRS 10g R2 Diagnostic Collection Guide

In addition to the CRS diagnostic collection guide for your particular version, please gather information

• from Cluster Health Monitor for platforms where it is available

  Start by reading Note 736752.1 – Introducing Cluster Health Monitor (IPD/OS)

• from OS Watcher, if available on your platform.

  OS Watcher is documented in:

  Note 301137.1 – OS Watcher User Guide

  Note.433472.1 – OS Watcher For Windows (OSWFW) User Guide

Please also gather the system messages files from all nodes – depending on your platform, these logs are found in different locations:

End of Node Reboot Section
=====================================

© 2009, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.

相关文章 | Related posts:

1. Data Gathering for Troubleshooting RAC Issues
2. Diagnosing Unsuccessful CRS root.sh Issues
3. Diagnosability for CRS / EVM / RACG
4. Troubleshooting Queries in Streams
5. UNIX: Checklist for Resolving Connect AS SYSDBA Issues
6. TROUBLESHOOTING: Tuning Queries That Cannot be Modified
7. Troubleshooting JVM Performance Problems
8. Troubleshooting Streams Capture when status is Paused For Flow Control
9. TROUBLESHOOTING: Possible Causes of Poor SQL Performance
10. Troubleshooting ORA-1031 Insufficient Privilege