Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

UNDO tablespace extent size - must it be 64K?

Status
Not open for further replies.

SJSFoxPro

Technical User
Jun 19, 2003
110
US
Question: in a database using locally managed tablespaces, is there any way to increase the extent size in the UNDO tablespace from 64K to 128K?

Background: we are trying to upgrade several of our 9i databases to 10g and are trying to establish some standards to use (for most databases). We have tried to create the UNDO tablespace as 128K without success. We have suspected that it has to be the same size as the SYSTEM tablespace
when using LMT, however cannot find any documentation to prove or disprove.

Any help, documentation, or other information would be greatly appreciated.

Susan
(Moved to Oracle)
 
Susan,

Since Oracle's default extent size for LMT is 64K, rather than try to "get an act of Congress" to override the default, would it not be easier to change your standard to 64K (especially since that is an automatic standard for all Oracle LMT tablespaces)?

[santa]Mufasa
(aka Dave of Sandy, Utah, USA)
[ Providing low-cost remote Database Admin services]
Click here to join Utah Oracle Users Group on Tek-Tips if you use Oracle in Utah USA.
 
In all of the documentation I have read, it appears that you remove the extent management clause for the UNDO tablespace (one of the benefits of using automatic undo management being the reduction of space management issues). However, in the Oracle9i SQL Reference, the create tablespace documentation includes UNDO tablespace and the extent management clause. It would have been helpful if there was an exception noted in the extent management clause that it can't be used for a create undo tablespace.

Basically, until I could prove and/or find definitive documentation stating that you cannot use the extent management clause with undo tablespace creation, I have a manager specifying that I use it.

I've found some documentation leading in that direction. If you can point me to anything else, please do.

I appreciate the comment you make. Perhaps it will be enough as you are so well known as an expert!

Thanks!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top