Oracle detailed monitoring not working when controlled by Cluster Server 5.1SP1

book

Article ID: 100006751

calendar_today

Updated On:

Description

Error Message

No specific error was seen. Instead, it was noticed that the Oracle database in question wasn't getting the relevant table concerned updated during any monitor. This was despite "DetailMonitor" being set to "1".

Resolution

From 5.1SP1, for detail monitoring to work, an additional attribute is required:

LevelTwoMonitorFreq

This was set to "1" as the example below reveals:

Oracle ora2_db (
                Critical = 0
                Owner = oracle
                User = bookie
                Table = timestamp
                DetailMonitor = 1
                Home = "/app/oracle/orahome"
                StartUpOpt = SRVCTLSTART
                MonScript = "/opt/VRTSagents/ha/bin/Oracle/SqlTest.pl"
                Sid @rgv200sol05 = punedb1
                Sid @rgv200sol06 = punedb2
                Pword = IURuLUuOJoKOl
                ShutDownOpt = SRVCTLSTOP
                LevelTwoMonitorFreq = 1
                )

Note that both LevelTwoMonitorFreq and DetailMonitor are set to "1". DetailMonitor is set to be deprecated from 6.0.

Applies To

RHEL 5.7

Storage Foundation HA for Oracle 5.1SP1

Issue/Introduction

It was determined that with detailed monitoring, Oracle database wasn't getting updated by the VCS Oracle agent.
Powered by Wolken Software