Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Usenet -> c.d.o.server -> Re: command line vs grid control

Re: command line vs grid control

From: DA Morgan <>
Date: Mon, 09 Jul 2007 15:41:01 -0700
Message-ID: <>

NetComrade wrote:
> On Thu, 05 Jul 2007 06:43:28 -0700, DA Morgan <>
> wrote:

>> wrote:
>>> On Jul 5, 12:08 am, DA Morgan <> wrote:
>>>> Waking up all night long and sniffing the air might be considered by
>>>> some less expensive than buying a smoke alarm.
>>>> I understand your point but to me it is the point of a dinosaur.
>>> Well, your advice is to throw out all the scripts and get on to grid
>>> control.
>>> My advice is, if you have money (and the size of your environment
>>> warrants this), get grid control; otherwise use database control plus
>>> scripts. If your scripts cover your requirements, nothing's wrong with
>>> keeping them. I think my position is more balanced and practical so
>>> I'll stick to it.
>> Given that it isn't your money and it isn't your data ... it belongs to
>> your employer ... I would bet that if the C-Level management of your
>> organization understood the difference between:
>> * The quality of monitoring: Oracle wins
>> * The fact that their code is tested: Oracle wins

> I wouldn't say testing was very good.. too many times have to use some
> kill -9 to try to stop a job that's been in 'stopping' state for a few
> hours (mostly backup jobs). It's also as slow as Sun's website,
> probably b/c both are running Java... well maybe not as slow, but
> still..
>> * The fact that with their code can call support: Oracle wins
>> * The fact that the Grid is documented: Oracle wins
>> * The fact that others can be hired that already know it: Oracle wins

Oh the shell scripts I could tell you about. <g>

The worst or Oracle's code is a magnitude or more better than the worst code I've seen thrown over cubicle walls.

Daniel A. Morgan
University of Washington (replace x with u to respond)
Puget Sound Oracle Users Group
Received on Mon Jul 09 2007 - 17:41:01 CDT

Original text of this message