Re: Adding new datafile question

drak0nian_at_yahoo.com (Paul Drake) wrote

> There were some bugs with filesizes of exactly 2 GB throwing errors.
> I don't recall exactly what versions (patchsets) they were fixed.

Been using 4GB as my standard datafile size for some time now in both 8i and 9i - no problems.

> I also used a command line comress utility that used to puke on files
> larger than 2 GB.

With exports and custom CSV unloads (some which results in a 5+ GB compressed file) I always use a pipe as the receiver (export/import dump file or spool file) and then run compress on it, writing to a destination file. Again, no problems.

Granted, back in the mid 90's there was still the issue with the Unix 2GB file limitation. But that is the past.

> Yes, it would be far better to plan/monitor/allocate sufficient space
> manually, but with where 10g is headed, I guess that we can start
> getting used to allowing oracle to manage such things more. But I
> still set maxsize on autoextend and get daily storage utilization
> reports emailed to me daily.

Yeah maybe... maybe not. I like sofware that automates the boring manual laborious tasks for me. I like software that assist me in making decisions. But I will not have software making decisions on my behalf. And auto extending data files fall into the latter category IMO. Simply because *you* as the dba do not know upfront what the actual space requirements are.

Which begs the question.. what the hell do you know about the rest of your database?

But then I still prefer command line over OEM, so maybe I'm just old fashioned (or should that be just old?).

--
Billy