Oracle database monitoring issues on Checkmk-v2

[srba]

CMK version: 2.0.0p12 (CEE) Enterprise Edition
**OS version:**Red Hat Enterprise Linux Server 7.7 (on Oracle database server)

Service configuration does not discover tablespaces and rman backup, all other Oracle services are discoverd.
Shutting down Oracle instance does not trigger a red CRIT status, only “the service is stale …” message.
Any idea what could be the reason?
Thank you.

[tosch (Tobias Schönau)]

Hi @srba,

can you please provide the output of the oracle sections and your DB version and if you are using RAC and/or ASM features? The output of MK_CONFDIR=/etc/check_mk/ /usr/lib/check_mk_agent/plugins/mk_oracle -t (may contains passwords) could also be handy.

[srba]

Hi @tosch,
Oracle database is version 19.14, no ASM/RAC is configured.
What do you mean under oracle section. Find below mk_oracle output.
[root@cm-rtdb-p-02:~]>export MK_CONFDIR=/etc/check_mk
[root@cm-rtdb-p-02:~]>/usr/lib/check_mk_agent/plugins/mk_oracle -t

---login----------------------------------------------------------------
    Operating System:       Linux
    ORACLE_HOME (oratab):   /u01/app/oracle/product/19.0.0.0/db
    Logincheck to Instance: cmrtdb
    Version:                19.0
    Login ok User:          CHECKMK on cm-rtdb-p-02 Instance cmrtdb
    SYNC_SECTIONS:          instance sessions logswitches undostat recovery_area processes recovery_status longactivesessions dataguard_stats performance locks systemparameter
    ASYNC_SECTIONS:         tablespaces rman jobs resumable iostats
------------------------------------------------------------------------

[srba]

Hi, just to add that the same issue faced on Oracle 19c database servers with Red Hat Linux 8.2 and Oracle Linux 8.4.

[awdi30 (Andreas Blank)]

Hey @srba
try the following solution:

Mk_oracle plugin problem

I have now been able to fix the problem locally by setting MK_ORA_DEBUG=true in /usr/lib/check_mk_agents/plugins/mk_oracle. After that change the cache file is created correctly and updated every CACHE_MAXAGE. After looking into the plugin i found that MK_ORA_DEBUG is used only once where the cache file is generated, so i suspect the problem must be there in the if then else fi statement. # Cache file outdated and new job not yet running? Start it if [ -z "$use_cache_file" ] && [ ! …

I had the same problem and this solved it.

[srba]

Thanks for recommendation. I changed MK_ORA_DEBUG=true, but unfortunatelly it still doesn’t work, the same issue again. Shutting down Oracle instance only reported stale status, tablespaces are not discoverd.