EXACHK VERSION: 18.4.0_20181129 Skipped/Killed Checks On Goldengate Environment
(Doc ID 2576298.1)
Last updated on SEPTEMBER 27, 2021
Applies to:
Oracle Exadata Storage Server Software - Version 18.1.7.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 18.1.7.0.0 version, Exachk utility issues
EXACHK VERSION: 18.4.0_20181129 skipped/Killed checks on Goldengate environment
Using the 18.4.0 Exachk we are getting Killed checks.
Many of the checks were successfully resolved by increasing RAT TIMEOUT parameters.
1)However the below kicked check will not resolve.
Killed check Oracle GoldenGate health check for 11.2.0.4 (CHECK-ID: E2D9FEDF1F3D125EE04313C0E50A840F) at xxx1client01 because it timed out
from exachk log we see:
ERROR
-----------------------
From log:
AUDIT CHECK NAME = Oracle GoldenGate health check for 11.2.0.4
2019-02-12 16:17:16,891 - INFO - __main__[(execute_checks)(log_fail)(18201)] - ------------------------------------------------------------
2019-02-12 16:17:16,896 - WARNING - __main__[(execute_checks)(run_checks)(2772)] - Skipping check(E2D9FEDF1F3D125EE04313C0E50A840F) on version 1 db_version=112040 versions_to_run=no-release 112040
Cause
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
Symptoms |
Cause |
Solution |