Werk #1901: mk_oracle: IGNORE_DB_NAME for special environments

Component	Checks & agents
Title	mk_oracle: IGNORE_DB_NAME for special environments
Date	Mar 29, 2015
Level	Trivial Change
Class	New Feature
Compatibility	Compatible - no manual interaction needed
Checkmk versions & editions	1.2.7i1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.7i1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.7i1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.7i1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.7i1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.7i1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.7i1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.7i1 Not yet released Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME) 1.2.7i1 Checkmk Raw (CRE), Checkmk Enterprise (CEE), Checkmk MSP (CME)

There are very rare environments, where databases use the same DB_NAME on 1 host. mk_oracle is not able to monitor such environments. This problem has been fixed with this change.

Important Note

When IGNORE_DB_NAME=1 is configured in mk_oracle.cfg the name of discovered checks will change from ORA <Database-Name> <Check> to ORA <Instance-Name> <Check>.

The monitoring of Real Application Clusters or Standby Environments is not possible with this parameter, because the checks don't use name which could be configured as a clustered service.

To the list of all Werks