Automatic TFA Self-Diagnostics on diagcollect Failure for Faster Issue Resolution

Autonomous Health Framework (AHF) introduces an enhancement to Trace File Analyzer (TFA) that improves troubleshooting efficiency when diagnostic collections fail.

With this feature, whenever the tfactl diagcollect command fails, TFA automatically triggers self-diagnostics using the tfactl diagnosetfa command. This ensures that relevant diagnostic data is immediately available for faster issue resolution.

During diagnostic data collection using tfactl diagcollect, failures can occasionally occur, preventing the successful gathering of logs required by Oracle Support. In such scenarios, users often lack clear guidance on next steps, resulting in delays and prolonged resolution times.

This enhancement eliminates that gap by introducing an automatic fallback mechanism that:

• Detects diagcollect failures
• Initiates TFA self-diagnostics automatically
• Provides clear instructions for next steps

Note:

• This feature currently applies only to manual collections executed by the root user
• In this initial phase:
• Diagnostics are collected only from the local node
• Remote-node failures require manual follow-up as instructed in the console

Key Benefits

• Automatic fallback execution

  Runs tfactl diagnosetfa automatically when diagcollect fails-no manual intervention required.

• Actionable guidance

  Clearly informs users about the failure and provides next-step instructions.

• Immediate diagnostic availability

  Generates a TFA self-diagnostics bundle for analysis by Oracle Support.

• Reduced resolution time

  Minimizes back-and-forth communication and accelerates troubleshooting.

Behavior and Workflow

When

tfactl diagcollect

fails, TFA automatically performs the following actions:

1. Detects the failure condition
2. Executes:

tfactl diagnosetfa -local -profile collection 3. Collects TFA/AHF self-diagnostics from the local node 4. Displays a message that includes:

- Confirmation of the failure
- Location of the generated diagnostic bundle
- Recommended next steps

The generated diagnostic file follows this format: hostname_ahf_autodiagnostic.zip

When Is Automatic Diagnostics Triggered?

The fallback mechanism is triggered when diagcollect fails due to conditions such as:

• TFA service interruption or restart during collection
• No progress for an extended duration and collector thread exit
• Fatal Failed DiagCollection error
• Collection Interrupted events, including:
• User-initiated termination
• Abrupt process termination
• Repository space-related aborts

Usage Instructions

Run Diagnostic Collection

tfactl diagcollect -since 2h or tfactl diagcollect -from "2026-01-20 10:00" -to "2026-01-20 12:00"

Expected Behavior

• If the command succeeds:

  Proceed with standard diagnostic upload and analysis.

• If the command fails:

  TFA automatically:

  • Executes diagnosetfa
  • Generates a diagnostic bundle
  • Displays instructions for uploading the bundle

Special Cases

Remote Node Failures

If diagcollect succeeds on the local node but fails on one or more remote nodes:

• The console identifies affected nodes
• You are instructed to run the following command on each affected node as root :

  tfactl diagnosetfa -local -profile collection

• Upload all generated bundles to the Service Request (SR)

Non-Root Execution

If diagcollect is run as a non-root user and fails:

• The console instructs you to rerun: tfactl diagnosetfa -local -profile collection as the root user on the local node
• Upload the generated bundle to the SR

Next Steps

1. Review the generated diagnosetfa bundle
2. Upload the file to your Service Request (SR) in My Oracle Support

3. Coordinate with Oracle Support for:

   • Root cause analysis of the failure
   • Guidance on collecting issue-specific diagnostics