Re: unable to extend table

Hi,

With Oracle7 v7.3, the maxextents clause limit was removed, and you can now say MAXEXTENTS UNLIMITED.

The other limit's that you are facing are those of datafile size limits. Most OS's recommend a limit off around 2Gb per data file, because this is what the Async I/O drivers can access on a 32bit machine, and since an Oracle Extent must reside in 1 and only 1 data file, here is the other limit you are facing. However check below for maximums.

Other limits are; maximum number of database blocks per datafile (4M for NT on 8.0.5), maximum number of datafiles (based upon block size). For 8.0.5 on NT check out Appendix B off the Getting Started Guide. However, I have not seen any documentation on the size of the INITIAL EXTENT clause.

Rgds
Andrew

gremlin wrote:

> Depending on how big the file will get, you can also turn autoextend on
> for it.
>
> I have a related question. I have a somewhat large database that I would
> like to set up an initial size for of, say, 15 Gigabytes. Oracle won't
> allow me to enter that in the "size" storage member for an alter table (or
> on the create table command). How do people manage VLDB's? Especially
> since there is a limited number of extents one can have (related to oracle
> block_size)? I also would like the extents to be around 2 Gig, but it
> doesn't want to accomodate me there either. Any ideas? (Besides
> pre-installing about 50 2 Gig .dbf files).
>
> Mike
>
> skb wrote:
>
> > Jim, you have to alter the tablespace and add another datafile.
> >
> > Jim Giza wrote:
> >
> > > Hello. I'm using Oracle 8 under Solaris. Have created a table with
> > > default settings, when I try to add a bunch for records, I get the
> > > following
> > > error. How do I go about allocating add'l space for the table?
> > >
> > > Thanks for any help.
> > >
> > > ORA-01653: unable to extend table OPS$USER.FEDEX_ZONES by 210 in
> > > tablespace
> > > USERS
>
> --
> -----------------------------------------------------
> To reply to me via email, remove the "__NO_SPAM__" in
> the header email address.
> -----------------------------------------------------
Received on Thu Apr 01 1999 - 00:15:46 CST