|
|
|
|
|
|
| Re: What is the max number of extents in Locally Manage TBS? [message #111794 is a reply to message #111773] |
Sun, 20 March 2005 16:46   |
smartin
Messages: 1803
Registered: March 2005
Location: Jacksonville, Florida
|
Senior Member |
|
|
It solves it within reason, but my question would be why 10,000? What is it you are trying to do? What are you planning for and what is your configuration? How many objects do you have and how are they accessed?
My first thought is that if you are trying to deal with 10,000 extents then you are probably doing something else wrong with your system. If you have a 10 gig object, why use 1 meg extents instead of a 32 meg. Why not partition? Why not use table compression and cut everything down in size?
It all depends on your system....
|
|
|
|
| Re: What is the max number of extents in Locally Manage TBS? [message #111974 is a reply to message #111794] |
Tue, 22 March 2005 03:23 |
d.c.b.a
Messages: 44
Registered: March 2005
Location: China
|
Member |
|
|
We faced this problem on dictionary managed tablespace, the extent number is about 60k, and we issue truncate table, the session blocked many other session, and take about 4 hours to finish this operation, and I think local management have many enhancement for this operation, but if extent number is too large, it do have some negative affection to the database.
Most of problem occurs when you database have thousands of connections.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
