There’s a saying, “There are old pilots and bold pilots, but very few old, bold
pilots”. I think that applies here. When I was a “practicing” DBA (before I
started working for a vendor), we ALWAYS had Autoextend off in our Production
databases, and in any database where running out of space could impact more
than a few developers. Of course, this DOES require that you understand your
applications and database usage, have good monitoring in place, and be
proactive as required to prevent “oops”; but those are all things that a
competent DBA should be doing anyway.
If for whatever reason you can’t do that – at least set maximums.
Clay Jackson
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Howard Latham
Sent: Thursday, February 4, 2021 7:49 AM
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: autoextend
CAUTION: This email originated from outside of the organization. Do not follow
guidance, click links, or open attachments unless you recognize the sender and
know the content is safe.
Oracle 19.
RH EL7
Good afternoon experts!
I am maybe andold fashioned DBA in that I prefer Autoextend to be turned off on
all our databases.
It's particularly risky when developers are allowed to 'develop' on the Prod
databases. (We are moving away from that)
Do you all allow autoextend or prohibit it?
Best Wishes
Howard