unable to extend index|table by 64000...
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: unable to extend index|table by 64000...

Hybrid View

  1. #1
    Join Date
    Oct 2002
    Posts
    1

    unable to extend index|table by 64000...

    Can someone help. I am running an oracle 8.1.7 on Linux.
    In one of my tablespaces, if I try to add a segment a following error occurs unable to extend ... by 64000. The initial extent is set to 1M then next extent is set to 1M the pctincrease is set to 0. For example if I create a table "create table xxx (num number) storage (initial 1M nextextent 1M pctincrease 0) tablespace bad_ts" then still the before mentioned error occurs. The tablespace is managed by dictionary. It happens only in bad_ts.

    Thanks for your help ...

    RR

  2. #2
    Join Date
    Nov 2001
    Location
    Singapore
    Posts
    182
    Hi ,

    The problem you are getting is due to max extent reached i.e tablespace fully occupied there is space left for new object to be created,enable auto extend of the file that belongs to tablespace or add one more datafile to the tablespace.
    J Gangadhar

  3. #3
    Join Date
    Jun 2003
    Location
    India
    Posts
    118
    Ur TS has reached to its MAXEXTENTS.

    Resize the datafile or add new datafile to that TS. I am not in favour of having autoextend option.
    vishal sood
    OCP 8

  4. #4
    Join Date
    Aug 2002
    Location
    Colorado Springs
    Posts
    5,253
    Originally posted by vishal sood
    I am not in favour of having autoextend option.
    I sense an interesting discussion -- why don't you favour it?
    David Aldridge,
    "The Oracle Sponge"

    Senior Manager, Business Intelligence Development
    XM Satellite Radio
    Washington, DC

    Oracle ACE

  5. #5
    Join Date
    Jul 2001
    Location
    Singapore(Asia)-WebCentre business company
    Posts
    456
    because by allow "auto-extend" u could potentially hit maximum datafile OS size limit 2GB for a single datafile in 32bit OS if i am not wrong?

  6. #6
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    Originally posted by vishal sood
    I am not in favour of having autoextend option.
    using that in production since Oracle 7.3.4

    no problems whatsoever

  7. #7
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    Originally posted by ngwh
    because by allow "auto-extend" u could potentially hit maximum datafile OS size limit 2GB for a single datafile in 32bit OS if i am not wrong?
    there is this parameter called MAXSIZE

  8. #8
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    why you guys are talking about maxextents? where in the error says it reached maxextents...? it says it cannot extend!

  9. #9
    Join Date
    Jul 2001
    Location
    Singapore(Asia)-WebCentre business company
    Posts
    456
    ohh..u mean if auto-extend is ON .. for version 7.3.4 onwards ORACLE itself will create a new datafile once file size limit has been reached? interesting...hee

  10. #10
    Join Date
    Jun 2003
    Location
    India
    Posts
    118
    Though it is(Autoextend) very useful feature but what I mean to say is, if we use Autoextend option the Oracle will itself extend the size of datafile after reaching MAXEXTENTS. If someone(lazy DBA) never checks the used/free space related things then one day he may find that the datafile has been ocupied/extended up to the whole avaialble space.
    vishal sood
    OCP 8

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width