Werk #15843: mk_oracle(ps1): Follow-up to privilege escalation fix
| Komponente | Checks & agents | ||||||
| Titel | mk_oracle(ps1): Follow-up to privilege escalation fix | ||||||
| Datum | 05.04.2024 | ||||||
| Level | Bedeutende Änderung | ||||||
| Klasse | Bugfix | ||||||
| Kompatibilität | Inkompatibel - Manuelle Interaktion könnte erforderlich sein | ||||||
| Checkmk versions & editions |
|
You might be affected by this Werk if you use mk_oracle on Windows.
Werk Werk #16232 introduced a regression, thereby disrupting Oracle monitoring on Windows.
This Werk addresses above mentioned issue that affects versions 2.1.0p41, 2.2.0p24, and 2.3.0b4.
Since this release, Oracle monitoring on Windows is fully supported under either of the following conditions: 1. The monitoring is performed using an account without administrator rights. 2. Specific Oracle executable binaries — namely, sqlplus.exe, tnsping.exe and, if presented, crsctl.exe - are not modifiable by non-admin users.
If you are still unable to monitor Oracle, for example, you can't use an unprivileged account for monitoring and changing of permission is not possible, consider one of the following actions: 1. Enable Run as local group for group Administrators in Run plugins and local checks using non-system account ruleset. 2. Adjust Oracle Binaries Permissions Check settings in ORACLE databases (Linux, Solaris, AIX, Windows) ruleset.
This plugin requires Powershell 5 or higher. You may need to update your Windows to monitor Oracle databases.
More information about can be found at here.