Re: command line vs grid control

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

>ivl5_at_hotmail.com wrote:
>> On Jul 5, 12:08 am, DA Morgan <damor..._at_psoug.org> 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

.......
We run Oracle 9iR2,10gR1/2 on RH4/RH3 and Solaris 10 (Sparc) remove NSPAM to email Received on Mon Jul 09 2007 - 15:25:41 CDT