DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: ideal Indexed Tablespace size for 150 to 200 Columns

  1. #1
    Join Date
    Mar 2002
    Posts
    25

    Question

    I have a separate indexed tablespace for all indexed columns averaging about 150 – 200 primary keys columns. I keep getting the ORA-01658: unable to create INITIAL extent for segment in tablespace.

    1. Is there any suggestion on ideal sizes for such a large groups of indexes? Please advice on ideal values for the Initial size, Next size, Min size, Increment size by, Minimum number, and Max number?

    2. Here is the storage parameters for when creating the Primary key column tablespace LOS_INDEX PCTFREE 10 STORAGE (INITIAL 2864K NEXT 1424K PCTINCREASE 50) - Is the storage parameter for each index too high or what?

    Please advice….

  2. #2
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    Depends, how many rows? What are your table sizes?
    Jeff Hunter

  3. #3
    Join Date
    Mar 2002
    Posts
    25

    Idexed Tablespace size for 150 - 200 columns

    The rows are approx 1 million and All my tables size are default as follows

    )
    TABLESPACE LOS_DATA NOLOGGING
    PCTFREE 10
    PCTUSED 40
    INITRANS 1
    MAXTRANS 255
    STORAGE (
    INITIAL 6569984
    NEXT 3276800
    PCTINCREASE 50
    MINEXTENTS 1
    MAXEXTENTS 121
    FREELISTS 1 FREELIST GROUPS 1 )
    NOCACHE;

    Any advise

  4. #4
    Join Date
    Apr 2001
    Location
    Brisbane, Queensland, Australia
    Posts
    1,203
    PCTINCREASE = 50.... yeach!.... fragmentation coming up. Set this to 0, and consider making INITIAL and NEXT the same size.
    OCP 8i, 9i DBA
    Brisbane Australia

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