9.38. Configuration for the oralck check
Prev Chapter 9. Configure the OpenSMART agents Next

9.38. Configuration for the oralck check

Check your oracle database for blocking locks existing longer then MAXAGE. This is useful for some cases (time critical batch jobs etc....)

locks will be identified by:

select count(*) from v$lock and blocking=1 and
                  ctime >= MAXAGE

You can define your maxage (paticulars in seconds)

ORALCK

Explanation

ORALCK is the enclosing tag for all databases to check.

Parent

OSAGENT

allowed values

Count

0 or 1. If you don't define ORALCK, no oralck check will run.

Example
<ORALCK>
  <DATABASE>
    <ORACLE_HOME>/usr/local/oracle/product/9.2.0</ORACLE_HOME>
    <ORACLE_SID>osmart</ORACLE_SID>
    <MAXAGE>400</MAXAGE>
    <ERRORLEVEL>WARNING</ERRORLEVEL>
  </DATABASE>
  <DATABASE>
    <ORACLE_HOME>/usr/local/oracle/product/9.2.0</ORACLE_HOME>
    <ORACLE_SID>osmart2</ORACLE_SID>
    <MAXAGE>150</MAXAGE>
    <ERRORLEVEL>FATAL</ERRORLEVEL>
    <DESCRIPTION>immediate kill the blocking session</DESCRIPTION>
  </DATABASE>
</ORALCK>

DATABASE

Explanation

for every database you want to check you you define the DATABASE-pair

Parent

ORALCK

allowed values

Count

As many as you like.

Example

Look at ORALCK

MAXAGE

Explanation

This entity describes the maximum of seconds a blocking lock may exists before it is recognized by an error.

Parent

DATABASE

allowed values

number (in seconds)

Count

1

Example
<ORALCK>
  <DATABASE>
    <ORACLE_HOME>/usr/local/oracle/product/9.2.0</ORACLE_HOME>
    <ORACLE_SID>osmart</ORACLE_SID>
    <MAXAGE>400</MAXAGE>
    <ERRORLEVEL>WARNING</ERRORLEVEL>
  </DATABASE>
  <DATABASE>
    <ORACLE_HOME>/usr/local/oracle/product/9.2.0</ORACLE_HOME>
    <ORACLE_SID>osmart2</ORACLE_SID>
    <MAXAGE>150</MAXAGE>
    <ERRORLEVEL>FATAL</ERRORLEVEL>
    <DESCRIPTION>immediate kill the blocking session</DESCRIPTION>
  </DATABASE>
</ORALCK>
Prev Up Next
9.37. Configuration for the orats check. Home 9.39. Configuration for the ping check