ORA-1652: unable to extend temp segment by 38400 in tablespace - Page 2
DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: ORA-1652: unable to extend temp segment by 38400 in tablespace

  1. #11
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    better run this

    select segment_name,segment_type, tablespace_name, next_extent, bytes
    from dba_segments where next_extent >= (38400 * 8192)

  2. #12
    Join Date
    Aug 2000
    Location
    Singapore
    Posts
    323
    Originally posted by pando
    better run this

    select segment_name,segment_type, tablespace_name, next_extent, bytes
    from dba_segments where next_extent >= (38400 * 8192)
    Thanks pando. Here is the result.

    SEGMENT_NAME
    --------------------------------------------------------------------------------
    SEGMENT_TYPE TABLESPACE_NAME NEXT_EXTENT BYTES
    ------------------ ------------------------------ ----------- ----------
    SYS_IL0000011225C00004$$
    LOBINDEX CASHIN_MST 314572800 314572800

    SYS_IL0000010344C00005$$
    LOBINDEX CASHIN_MST 314572800 314572800

    SYS_LOB0000011225C00004$$
    LOBSEGMENT CASHIN_MST 314572800 314572800

    SYS_LOB0000010344C00005$$
    LOBSEGMENT CASHIN_MST 314572800 314572800

    Thanks In advance
    Nagesh

  3. #13
    Join Date
    Sep 2003
    Location
    Bangalore
    Posts
    36

    Post

    Hi,
    Thought just explain that there is nothing much to fear about this error. This error usuaully occurs when some process tries to create a temp segment in a tablespace be it temporary or permanent. WE have to understand that temp segment does not always mean that there is a sort operation involved. During DDL commands also such temp segments are required and hence if such an operation is big, for a particular tablesapce such error occurs. This keeps happening when new objects are created like indexes, table, constraints etc.
    Hence see if any user was trying to create a object. The best solution is to coalesce the tablespace and most of the cases the problem will get solved. Else if the operation which failed is essential then add space to the tablespace.
    This also happens during index rebuild, table move etc.
    This is not a very severe error.
    Thanks
    Regards

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