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

Thread: resize datafile fails

  1. #1
    Join Date
    Aug 2000
    Posts
    163
    I have a rollback tablespace datafile. When I look at the tablespace through GUI tool it shows 2750m allocated 1813.73m used. When I am trying to reduce the size of the datafile to 2200m I get an error:ORA-03297 'FILE CONTAINS 115845 BLOCKS BEYOND REQUESTED RESIZE VALUE'.
    I've already tried to coalesce that tablespace. It didn't change anything.
    What is going on? What do I do?

  2. #2
    Join Date
    Feb 2000
    Location
    Washington DC
    Posts
    1,843
    Seems you have segments spread in the portion you are trying trim off. Thats means Just because its showing less means you could resize it. It depends on where the segments have been spread.

    You can give a try wehrn there is nothing in Rollback, I mean whenever you bounce database.

    <font face=courier>
    03297, 00000, "file contains used data beyond requested RESIZE value"
    // *Cause: Some portion of the file in the region to be trimmed is
    // currently in use by a database object
    // *Action: Drop or move segments containing extents in this region prior to
    // resizing the file, or choose a resize value such that only free
    // space is in the trimmed.
    </font>
    Reddy,Sam

  3. #3
    Join Date
    Aug 2000
    Posts
    163
    Sheddy, you mean I can try to do the same resize thing when through server manager? If that is correct, what state my database shall be open in?

  4. #4
    Join Date
    Feb 2000
    Location
    Washington DC
    Posts
    1,843
    No big deal. you can find the rollback segments that doesn't have active transactiopns and drop couple of 'em and then try resizing it. it should work. You don't need to bring database down.
    Reddy,Sam

  5. #5
    Join Date
    Oct 2000
    Posts
    80

    What you're describing is natural behavior for rollback tablespaces. If you look at tablespace manager it may show you the segments that are at the end of the datafile.
    Even if you do drop the offending segments, your tablespace will be back to the behavior in short order. The proactive method is to size rollback segments appropriately to minimize extensions. Check the documentation or tuning books to get the scoop. Do this primarily by setting minextents to 20, and picking an extent size such that 20 of them will accomodate your largest average transaction. Set optimal = minextents*initial.
    John Doyle

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