Morris, Patrick wrote:
>>> I'm not sure how the tablespace check would work
>>> with auto-extending tablespaces if you use them.
>>
>> I'm curous about that myself. Anybody know?
>
> It doesn't work well. :)
>
> Because auto-extending tables tend to live n the edge of their
> available space, th
Jim Avery wrote:
> I confess I haven't used these yet myself (probably ought to though).
> The ones I would immediately pick are:
>
> check_oracle --tns and
> check_oracle --tablespace
>
> I probably wouldn't bother with most of the others on the principle
> that if I can't interrogate the
Phil Costelloe wrote:
> Jim Avery wrote:
>> I confess I haven't used these yet myself (probably ought to though).
>> The ones I would immediately pick are:
>>
>> check_oracle --tns and
>> check_oracle --tablespace
>>
>> I probably wouldn't bother with most of the others on the principle
>> t
> > I'm not sure how the tablespace check would work
> > with auto-extending tablespaces if you use them.
>
> I'm curous about that myself. Anybody know?
It doesn't work well. :)
Because auto-extending tables tend to live n the edge of their available
space, this check will almost always repo
I confess I haven't used these yet myself (probably ought to though).
The ones I would immediately pick are:
check_oracle --tns
and
check_oracle --tablespace
I probably wouldn't bother with most of the others on the principle
that if I can't interrogate the tablespaces, I can't connect to th
I just "check_oracle --login dbname"since this tells me if the server is
reachable, if the login prompt is given correctly and if there are any
problems, they are raised with the ORA- error message so at all time
I know what the exact condition or error of the database is.
-h
Hari Sekhon
Hi,
I need to monitor an oracle database ( on debian ). I played with the
"check_oracle --tns 127.0.0.1" over ssh
And thats returns green ok ! So far so good.
But what other checks are useful to do or even better like the --login option
or do need to check them all
... i'm not home at or
