SRDC - ORA-600 / ORA-700 / ORA-7445: Checklist of Evidence to Supply for Version 11g and Greater (Doc ID 2165632.1)


27-Apr-2019 DIAGNOSTIC TOOLS
   
Rate this document Email link to this document Open document in new window Printable Page
Applies To

Product:

  • Operating System: All
  • Version 11+
What is being collected and why?

Oracle Support strongly recommends using Trace File Analyzer (TFA) Collector for collecting data. TFA Collector has been included in the Autonomous Health Framework (AHF).

Reference - Document 2550798.1 Autonomous Health Framework (AHF) - Including TFA and EXAchk

This SRDC will collect the information needed to start the analysis of error ORA-600, ORA-700 or ORA-7445. 

Safe Harbor Statement: Oracle will use this information to help diagnose the cause of the issue. In many cases this set of information will be sufficient for diagnosis - in some cases, additional specific diagnostic data may be required at a later stage.

Action Plan

Auto Collection Using TFA

1. Download and install the latest version of TFA using the AHF installer: Download AHF

2. Using AutoCollection:

a. Ensure that autocollection is enabled: tfactl set autocollection on
b. If AutoCollection is already enabled and an ORA-600/ORA-7445/ORA-700 is observed, the collection will be automatically created at the time of the error and will be in the location you have defined for output.
c. If AutoCollection is not enabled and an ORA-600/ORA-7445/ORA-700 is observed, you will need to perform the SRDC collection manually as the oracle software owner: This lets you select an event or prompt for an incident timestamp (YYYY-MM-DD HH24:MI:SS) to trim and collect data from 1 hour around the provided time.

  • ORA-600

$TFA_HOME/bin/tfactl diagcollect -srdc ora600

  • ORA-700

$TFA_HOME/bin/tfactl diagcollect -srdc ora7445

  • ORA-7445

$TFA_HOME/bin/tfactl diagcollect -srdc ora700

3.  Upload the resulting zip file *exactly as it is generated* to the Service Request (SR)

 

 

 

For both cases, TFA collection or manual instructions:

Optional but recommended: Testcase (for reproducible issues)

        See Document 232963.1 for how to isolate a testcase.

To BottomTo Bottom
posted @   耀阳居士  阅读(243)  评论(0编辑  收藏  举报
编辑推荐:
· 没有源码,如何修改代码逻辑?
· 一个奇形怪状的面试题:Bean中的CHM要不要加volatile?
· [.NET]调用本地 Deepseek 模型
· 一个费力不讨好的项目,让我损失了近一半的绩效!
· .NET Core 托管堆内存泄露/CPU异常的常见思路
阅读排行:
· 微软正式发布.NET 10 Preview 1:开启下一代开发框架新篇章
· 没有源码,如何修改代码逻辑?
· PowerShell开发游戏 · 打蜜蜂
· 在鹅厂做java开发是什么体验
· 凌晨三点救火实录:Java内存泄漏的七个神坑,你至少踩过三个!
点击右上角即可分享
微信分享提示