Question

Options

• A$ ${ORACLE_HOME}/suptools/tfa/release/tfa_home/bin/tfact1 --from <Fridays_Date>_17:00:00 --
• B

  /opt/oracle.SupportTools/ibdiagtools/netcheck/runDiagnostics.pm --from

• C

  /opt/oracle.ExaWatcher/GetExaWatcherResults.sh --from <Fridays_Date>_17:00:00 --to

• D

  /opt/oracle.SupportTools/exachk/exachk --from <Fridays_Date>_17:00:00 --to

• A
  9% (4)
• B
  2% (1)
• C
  82% (36)
• D
  7% (3)

Explanation

ExaWatcher (GetExaWatcherResults.sh) is the correct tool because it continuously records Exadata system metrics - including client network activity - and supports --from/--to time-range parameters, making it purpose-built for reconstructing what happened during a specific historical window like a weekend outage.

• A is wrong because tfactl (TFA/Trace File Analyzer) collects diagnostic bundles and log files reactively; it's not designed to query historical network telemetry by time range, and the command shown (tfact1) is misspelled.
• B is wrong because ibdiagtools/netcheck targets the InfiniBand interconnect (the internal Exadata fabric between nodes), not the client network (Ethernet) that external databases users connect through.
• D is wrong because exachk is a health and best-practices compliance checker that produces configuration reports - it has no mechanism to investigate past network communication events.

Memory tip: "ExaWatcher watches your Exadata 24/7" - think of it as security camera footage you can rewind to any timestamp with --from/--to.

No community discussion yet for this question.