Checkmk Entreprise 1.6.0 p19
I have noticed the issue monitoring Oracle 19c on Oracle Linux 8.2.
When I shutdown database Oracle instance service is still in OK state, no alarm shows up.
Has anyone experienced similar issue?
Thank you
2 questions on that:
- Is the service really in OK state - or is it stale?
- Do you have specific state configurations in WATO, e.g. Parameters for discovered services >> Applications, Processes & Services >> Oracle Instance where OK as state is defined for your case?
Hi,
- You are right, after shutting down all Oracle services become stale.
- No specific state configuration in WATO, no issue with Oracle 11g, 12c
Interesting… We were testing the mk_oracle as well for further usage and I remember the service for the oracle instance was reporting a WARN or CRIT instead of only stale status if the database was no longer available.
Maybe in a first step you could update the plugin itself if you are using an older version? There are several checkmk werks related to the oracle plugin and even some especially for 19c, e.g. Werk #8804: mk_oracle: Fixed compatibility to oracle 19c.
I applied pretty new Oracle plugin from 2019, please find the beginning bellow
My version is Checkmk Entreprise 1.6.0 p19 and I am not sure which werk to apply, you mention werk for version Checkmk Raw 1.5.0p22. I have no expirence with applying werks.
#!/bin/bash
Copyright © 2019 tribe29 GmbH - License: GNU General Public License v2
This file is part of Checkmk (https://checkmk.com). It is subject to the terms and
conditions defined in the file COPYING, which is part of this source code package.
Check_MK agent plugin for monitoring ORACLE databases
This plugin is a result of the common work of Thorsten Bruhns
and Mathias Kettner. Thorsten is responsible for the ORACLE
stuff, Mathias for the shell hacking…
This plugin works for Linux, Solaris and AIX.
See http://mathias-kettner.de/cms_monitoring_oracle.html
for more details regarding configuration.
TODO
- cleanup ORACLE_SID, MK_SID, local sid
- separate remote instance, local, ASM
.–default config------------------------------------------------------.
| _ __ _ _ __ _ |
| __| | ___ / _| __ _ _ | | | ___ ___ _ __ / () __ _ |
| / |/ _ \ |_ / _ | | | | | __| / _/ _ | ’ | || |/ _` | |
| | (| | __/ | (| | || | | |_ | (| () | | | | | | (| | |
| _,|_|| _,|_,||__| ____/|| ||| ||__, | |
| |___/ |
‘----------------------------------------------------------------------’
I just mentioned the werk as an example because it’s related to oracle 19c and therefore indicating that some changes in the plugin have been implemented w.r.t. to 19c which might be of interest here.
- If this werk is relevant you should cross-check if you are using a plugin version of mk_oracle that contains these changes and that has been delivered with / since the relevant version 1.5.0p22 (as annotated in the afore mentioned werk).
- As you are using 1.6.0p19 your installation should include the updated checks on server-side (published with 1.5.0p22 due to werk #8804)
Do you observe differences when using the same plugin version for different oracle versions w.r.t. stale instance service?
Maybe you could check the server-side checks for the instance service if there’s (new) code resulting in a stale service instead of WARN / CRIT. - As mentioned before, I’d also expect a WARN / CRIT state instead of stale, see Check manual page of oracle_instance: "... The state is CRITICAL when logins are not possible ..."
Thank you for your answers.
I applied this version of plugin on many database servers. I faced the same issue on several database servers with Oracle 19c. On other servers with Oracle 11g and 12c no issue has been noticed. Besides, all database servers have standard installation and configurtaion, no additional code resulting in a stale service. Maybe some incompatibility with Oracle 19c could be the reason for this issue?
In this case you should report your observations to tribe29 via issue / ticket and ask for help resp. explanation about the plugin’s behaviour. I don’t think other customers using the oracle plugin would expect stale instance services after upgrading to 19c as soon as the database is offline.
Would be great to read your progress or further instructions here if you get in contact with tribe29. 
Hopefully tribe29 can provide a solution which I will share here.
Thank you.
Root cause of this issue was wrong plugin. I will provide heading lines of both plugins, wrong and right one.
WRONG PLUGIN:
#!/bin/bash
Copyright © 2019 tribe29 GmbH - License: GNU General Public License v2
This file is part of Checkmk (https://checkmk.com). It is subject to the terms and
conditions defined in the file COPYING, which is part of this source code package.
Check_MK agent plugin for monitoring ORACLE databases
This plugin is a result of the common work of Thorsten Bruhns
and Mathias Kettner. Thorsten is responsible for the ORACLE
stuff, Mathias for the shell hacking…
This plugin works for Linux, Solaris and AIX.
See http://mathias-kettner.de/cms_monitoring_oracle.html
for more details regarding configuration.
TODO
- cleanup ORACLE_SID, MK_SID, local sid
- separate remote instance, local, ASM
.–default config------------------------------------------------------.
| _ __ _ _ __ _ |
| __| | ___ / _| __ _ _ | | | ___ ___ _ __ / () __ _ |
| / |/ _ \ |_ / _ | | | | | __| / _/ _ | ’ | || |/ _` | |
| | (| | __/ | (| | || | | |_ | (| () | | | | | | (| | |
| _,|_|| _,|_,||__| ____/|| ||| ||__, | |
| |___/ |
‘----------------------------------------------------------------------’
RIGHT PLUGIN:
#!/bin/bash
±-----------------------------------------------------------------+
| ____ _ _ __ __ _ __ |
| / _| | ___ ___| | __ | / | |/ / |
| | | | '_ \ / _ / __| |/ / | |/| | ’ / |
| | |___| | | | / (| < | | | | . \ |
| _|| ||_|_||___|| |||_\ |
| |
| Copyright Mathias Kettner 2014 mk@mathias-kettner.de |
±-----------------------------------------------------------------+
This file is part of Check_MK.
The official homepage is at http://mathias-kettner.de/check_mk.
check_mk is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by
the Free Software Foundation in version 2. check_mk is distributed
in the hope that it will be useful, but WITHOUT ANY WARRANTY; with-
out even the implied warranty of MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE. See the GNU General Public License for more de-
tails. You should have received a copy of the GNU General Public
License along with GNU Make; see the file COPYING. If not, write
to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor,
Boston, MA 02110-1301 USA.
Check_MK agent plugin for monitoring ORACLE databases
This plugin is a result of the common work of Thorsten Bruhns
and Mathias Kettner. Thorsten is responsible for the ORACLE
stuff, Mathias for the shell hacking…
This plugin works for Linux, Solaris and AIX.
See http://mathias-kettner.de/cms_monitoring_oracle.html
for more details regarding configuration.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.