Fabrizio wrote:
> Frank van Bortel wrote:
>
>> Antoine BRUNEL wrote:
>>
>>> .... a DBA is supposed to know why ....
>>>
>>> an example: something goes wrong with the nightly batch, and you
>>> allow dbfiles to grows without limits.... the filesystem become full,
>>> with a little chance, archive destination too, and instance freeze....
>>>
>>>
>>>
>>>
>>>
>>> "Frank van Bortel" <fvanbortel_at_netscape.net> a écrit dans le message
>>> de news: csbsvu$p2m$1_at_news5.zwoll1.ov.home.nl...
>>>
>>>> Antoine BRUNEL wrote:
>>>> [snip!]
>>>>
>>>>
>>>>> anyway, it is strongly recommended that you control dbfiles sizes
>>>>> by yourself, and not let them increase automatically.....
>>>>>
>>>>
>>>> and why would that be? Lazy-DBA syndrome?
>>>>
>>>> --
>>>> Regards,
>>>> Frank van Bortel
>>>
>>>
>>>
>>>
>>>
>> Pls, don't top post.
>>
>> I'm not a DBA, I have never claimed to be.
>>
>> And you stated you would advise against the use
>> of autoextending files, no word about limiting
>> the growth.
>> If used, use with:
>> a) reasonable sized chuncks, and:
>> b) a maximum file size (maxsize option)
>>
>> I see no harm in that, but I understand you would
>> rather have your nightly batches fail? :-^
>
>
> Sometime is convenient to have fixed size datafiles...
> others it is not a good idea to have autoextend on. Raw devices don't
> like it (I don't see the point to have "max size" and a datafile smaller
> than its raw device).
>
> I wouldn't even like to have autoextend on with tablespaces with
> autoallocate policies... (just personal feeling).
>
> Regards
>
Ah - touche! You have a point; of course.
--
Regards,
Frank van Bortel
Received on Tue Jan 18 2005 - 04:25:03 CST
