My Oracle Support Banner

Skipped Checks And Timeouts In Exachk Report -Exachk 20.4 (Doc ID 2750457.1)

Last updated on APRIL 12, 2022

Applies to:

Oracle Exadata Storage Server Software - Version 20.1.4.0.0 and later
Information in this document applies to any platform.

Goal

Few checks are timed out in Exachk report.
Tried also with below parameters but issue remains

RAT_PROMPT_TIMEOUT=30
RAT_TIMEOUT=300
RAT_REMOTE_RUN_TIMEOUT=10800
RAT_PASSWORDCHECK_TIMEOUT=10
RAT_PROMPT_WAIT_TIMEOUT=60

Killed Processes
-----------------
exachk found that below commands were killed during the run, so some checks might have failed to execute properly. Refer to the "Slow Performance, Skipped Checks, and Timeouts" section of the user guide for corrective actions.

Killed check Verify database server quorum disks configuration (Check-ID: 339FE456FBDC3549E0530D98EB0AD21F) at oex10db01 because it timed out
Killed check Verify ACFS filesystems and critical database files are not in the same ASM disk group (Check-ID: 8ABBA0EAA5F1B005E053D198EB0A3B30) at oex10db01 because it timed out
Killed check Verify Oracle Clusterware files are placed appropriately (Check-ID: A096611C3310AC86E053D598EB0A3C1B) at oex10db01 because it timed out
Killed check Verify database server quorum disks configuration (Check-ID: 339FE456FBDC3549E0530D98EB0AD21F) at oex10db02 because it timed out
Killed check Verify Oracle Clusterware files are placed appropriately (Check-ID: A096611C3310AC86E053D598EB0A3C1B) at oex10db02 because it timed out
Killed check Verify database server quorum disks configuration (Check-ID: 339FE456FBDC3549E0530D98EB0AD21F) at oex10db03 because it timed out
Killed check Verify Oracle Clusterware files are placed appropriately (Check-ID: A096611C3310AC86E053D598EB0A3C1B) at oex10db03 because it timed out
Killed check Verify database server quorum disks configuration (Check-ID: 339FE456FBDC3549E0530D98EB0AD21F) at oex10db04 because it timed out
Killed check Verify Oracle Clusterware files are placed appropriately (Check-ID: A096611C3310AC86E053D598EB0A3C1B) at oex10db04 because it timed out

[root@DBNODE1 ~]# exachk -v
EXACHK VERSION: 20.4.0_20201214
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.