The "Planning Extents" tip on the Ixora web site explains why all segments
should have a modest number of extents. This is most important in dictionary
managed tablespaces, but applies to locally managed tablespaces as well. In my
opinion, the unlimited extents feature just gives DBAs an unlimited amount of
rope with which to hang themselves. The MAXEXTENTS limit should be looked upon
as a protection, not a threat. It can cause a rogue job to fail earlier rather
than later when it has had less opportunity to do damage. Therefore, MAXEXTENTS
should be set to a value that will give you the required level of protection,
without risk of hitting the limit during routine database operation. UNLIMITED
gives you no such protection.


-----Original Message-----
Sent: Wednesday, 30 August 2000 17:08


I'm interested in your opinion about maxextents setting. Is it a bad choice to
use maxextents = unlimited as a common decision? I've read some articles. They
recommended using maxextents = unlimited.