AHF - Autonomous Health Framework (TFA - ORACHK) (MOSC)

MOSC Banner

AHF V21.2 Beta : Exachk reporting incorrect CRITICAL checks

in AHF - Autonomous Health Framework (TFA - ORACHK) (MOSC) Question

Installed AHF v21.2Beta on QA Exadatas and ran exachk against Cluster 1 ... in reviewing the results , exachk is reporting the following critical issues on all Servers/ASM Instances :

System is exposed to Exadata Critical Issue DB49

System is exposed to Exadata Critical Issue DB48

System is exposed to Exadata critical issue DB47

Reviewed the Docs Provided/Referenced:

Exadata Critical Issues (Doc ID 1270094.1)

(DB49) One or more Exadata database nodes evict after fabric switch reboot (Doc ID 2772815.1)

(DB48) Clusterware reconfiguration hang after node eviction can lead to cluster-wide outage (Doc ID 2770035.1)

(DB47) Disk offline/online/offline may cause database corruption (Doc ID 2680856.1

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center