DA Morgan wrote:
> Jim Kennedy wrote:
>
>>> Hm - never had trouble with it, but yes, it could happen, when
>>> the chunks to grow with are large, and the (file-)system is
>>> heavily loaded. It is a point to be considered (isn't it all?)
>>> when using it; the size with with to grow should be reasonable.
>>>
>>> --
>>> Regards,
>>> Frank van Bortel
>>
>>
>> But being slow is better than being down. (eg the tablespace is out of
>> room
>> vs the tablespace has to grow 250megs and takes 10 to 20 seconds)
>> Jim
>
>
> Not sure I agree.
>
> The difference is that if it goes down it is obvious the DBA has not
> been paying attention, not doing a good job, and needs some remedial
> education or a trip to the unemployment line to remind them why they
> are being paid. The "slows down" gives the incompetent DBA more paid
> hours to diagnose the issue and blame it on someone else.
>
> I vote to let the thing break and let management dump the offender on
> the other side of the door. There should be consequences for not paying
> attention to tablespaces and alert logs.
So, lazy DBA syndrome it is...
Oh well, take some time, and it will be accepted, just
as all these other features since V5.
--
Regards,
Frank van Bortel
Received on Mon Jan 17 2005 - 06:10:50 CST
