| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: automatic extent allocation
2147483645=20
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-----Original Message-----
From: Roger Xu [mailto:roger_xu_at_dp7uptx.com]=20
Sent: Friday, January 07, 2005 3:53 PM
To: Jonathan Lewis; Oracle-L_at_Freelists. Org (E-mail)
Subject: RE: automatic extent allocation
So the suggestion would be to move it to its
own tablespace with uniform extent allocation?
What is Oracle 9i's limit as far as the number
of extents in a table? Thanks.
-----Original Message-----
From: Jonathan Lewis [ mailto:jonathan_at_jlcomp.demon.co.uk]
Sent: Friday, January 07, 2005 2:33 AM
To: Roger Xu; Oracle-L_at_Freelists. Org (E-mail)
Subject: Re: automatic extent allocation
In the first place, I would consider moving the object out of the current tablespace (or move everything else out of the tablespace) because it sounds like nothing else should be sharing that tablespace. (Consider the problem of recovering the entire tablespace because one of the other tables gets a corrupt block - if you can't take advantage of rman block level recovery).
Secondly, at 3GB per month, I would consider partitioning the table at something like one partition per month - thus making your question moot.
It sounds like your object is still using 64MB extents - it would be interesting to see if there is another step size when you hit a total of 64GB, or whether you keep going at 50 extents per month.
I suspect the problems you __might__ get from having 2,000 extents are much less significant than the problems you __might__ get if you have a 100GB segment by the end of next year.
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/seminar.html Public Appearances - schedule updated Dec 23rd 2004
Hi list,
We are on Solaris 9/Oracle 9i with locally managed tablespace.
There is a huge tablespace in our database with many huge tables.
The biggest table has a size of 60 GB. (Indexes are in a different
tablespace)
And it has 1030 extents now, because we use automatic extent allocation.
Right now we do not have any issues. Do you recommend me to move it to
its
own tablespace with uniform extent allocation? At what point are we
going to
have issue? over 2000 extents? The table is growing at a rate of 3 GB /
month.
TIA,
Roger
This e-mail is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged information.
Any
review, dissemination, copying, printing or other use of this e-mail by
persons or entities other than the addressee is prohibited. If you have
received this e-mail in error, please contact the sender immediately and
delete the material.
For technical support please email tech_support_at_dp7uptx.com or you can
call (972)721-8257.
This email has been scanned for all viruses by the MessageLabs Email
Security System.
This e-mail is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. Any review, dissemination, copying, printing or other use of this e-mail by persons or entities other than the addressee is prohibited. If you have received this e-mail in error, please contact the sender immediately and delete the material.=20
 |
 |