- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: rollback segment (rbs) reach to max extents
Operating System - HP-UX
1752793
Members
6234
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2001 09:12 PM
тАО06-25-2001 09:12 PM
If my rbs tablespace shown reach to max extents, should i increase the max extents value or increase datafile ?? Please help.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-25-2001 10:41 PM
тАО06-25-2001 10:41 PM
Solution
Hi there.
You should count the number of rollback segs, the number of maxextents for these and the size of the rollback segs and the size of the tablespace for the rollback segs.
if #rollbacksegs x size_rollbacksegs x maxextents of rollbacksegs > tablespace, enhance the tablespace.
Sample :
5 rollback segs
size 10M
extent size 10M
maxextents 10
5 x 10 x 10 = 500M for the tablespace.
If the result is lt than the tablespace size,
try to distribute the rest of the tablespace to the rollbacksegs extents.
If you need more explanation, contact me
at Alexander_Ermes@web.de
Rgds
Alexander M. Ermes
You should count the number of rollback segs, the number of maxextents for these and the size of the rollback segs and the size of the tablespace for the rollback segs.
if #rollbacksegs x size_rollbacksegs x maxextents of rollbacksegs > tablespace, enhance the tablespace.
Sample :
5 rollback segs
size 10M
extent size 10M
maxextents 10
5 x 10 x 10 = 500M for the tablespace.
If the result is lt than the tablespace size,
try to distribute the rest of the tablespace to the rollbacksegs extents.
If you need more explanation, contact me
at Alexander_Ermes@web.de
Rgds
Alexander M. Ermes
.. and all these memories are going to vanish like tears in the rain! final words from Rutger Hauer in "Blade Runner"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2001 02:56 AM
тАО06-26-2001 02:56 AM
Re: rollback segment (rbs) reach to max extents
Hello CHEN,
Alexander is right in most cases. One thing to consider in addition if you have OLTP application, is that you should configure an OPTIMAL size, to shrink the rollback segments automaticly.
If you have a setup like that, you should give NEXT and MAX_EXTENTS values so that one rollback segment can use the entire space if needed.
Example:
2GB RBS tablespace
5 rollback segments
transactions_per_rollback_segment = 10 (init.ora)
average rollback load per transaction i.e. 1MB
-> You should monitor V$ROLLSTAT to get a feeling for this value, but do not choose a too low value
=> This would lead me to an OPTIMAL SIZE of around 10MB for one rollback segment, so for standard load 10 transactions in one RBS will not need to allocate new extents, because 10MB would be enough.
So assuming 5 segments, around 50 MB will be used minimum.
If one user fires a big transaction, the rbs in charge should be able to groe up to 2 GB.
So in this case I would go for the following values:
MINEXTENTS = 3
NEXT = INITIAL = 4MB
MAXEXTENTS = 500
OPTIMAL = 12MB
Very important is to have all extents in this tablespace with the same size, if you configure an optimal value, so the freespace will not be fragmented after shrinks.
Hope this helps
Volker
Alexander is right in most cases. One thing to consider in addition if you have OLTP application, is that you should configure an OPTIMAL size, to shrink the rollback segments automaticly.
If you have a setup like that, you should give NEXT and MAX_EXTENTS values so that one rollback segment can use the entire space if needed.
Example:
2GB RBS tablespace
5 rollback segments
transactions_per_rollback_segment = 10 (init.ora)
average rollback load per transaction i.e. 1MB
-> You should monitor V$ROLLSTAT to get a feeling for this value, but do not choose a too low value
=> This would lead me to an OPTIMAL SIZE of around 10MB for one rollback segment, so for standard load 10 transactions in one RBS will not need to allocate new extents, because 10MB would be enough.
So assuming 5 segments, around 50 MB will be used minimum.
If one user fires a big transaction, the rbs in charge should be able to groe up to 2 GB.
So in this case I would go for the following values:
MINEXTENTS = 3
NEXT = INITIAL = 4MB
MAXEXTENTS = 500
OPTIMAL = 12MB
Very important is to have all extents in this tablespace with the same size, if you configure an optimal value, so the freespace will not be fragmented after shrinks.
Hope this helps
Volker
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP