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

MOSC Banner

How do I prevent from exachk to run specific checks on my standby databases?

edited Aug 8, 2023 6:03AM in AHF - Autonomous Health Framework (TFA - ORACHK) (MOSC) Question

Grid Infrastructure and DB homes version 19.17

AHF version 23.5.0.0.0

exachk is running the following check against my standby database (only on node #1) and failing cause it should be running on an open primary database only:

ID: 1005EE0B4A44119CE05312C0E50AE55B

FAIL

NA

Database CheckThe bundle patch version installed does not match the bundle patch version registered in the database

When exachk is doing discovery, how is it deciding on which db to run checks, if its a standby or primary databases?

I do not want to use excludedbnames (Some checks are still needed).


Edit:

after rechecking crsctl status, I noticed the the state for the instance was:

Tagged:

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