RE: 2GB or not 2GB (datafile limit)? That is the question.

  • From: "Powell, Mark D" <mark.powell@xxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 8 Sep 2006 10:46:10 -0400

Rich, I think the answer depends on your OS.  If the OS is configured to
handle datafiles of 32G or larger then leave the setting alone.  If your
OS have a 4G file limit then change the settings and monitor the
tablespace file space usage more closely than you would need to with a
32G file.  

HTH -- Mark D Powell --

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jesse, Rich
Sent: Friday, September 08, 2006 10:17 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: 2GB or not 2GB (datafile limit)? That is the question.

Many moons ago, way back in the 32-bit era when Y2K was a looming
nightmare, I had instituted a policy that no Oracle datafile would be
setup to grow larger than 2GB.  This was due to some known bugs with
files larger than 2GB on many platforms/filesystems at the time.

As I'm now looking at a vendor's ERP installation, I was about to reduce
their max datafile size from 32GB to 2GB when I asked myself "Why?".  Is
there any valid sane reason to do this anymore?  I do not expect the DB
size to grow beyond a modest 100GB in the next two years.  The server is
an IBM P5 blade running AIX5.3 and using JFS filesystems.  Other similar
servers with other DBs (e.g. Sybase) currently handle db files in the
100's of GB with no problem.

I don't see any need to limit the datafile size to 2GB anymore.  Anyone



Other related posts: