You Look At The Dba_rollback_segs View And See That You Have A Large

1.	You Look At The Dba_rollback_segs View And See That You Have A Large Number Of Wraps Is This A Problem?
Answer» A large NUMBER of wraps indicates that your extent size for your rollback segments are probably too SMALL. INCREASE the size of your extents to reduce the number of wraps. You can look at the average transaction size in the same view to GET the information on transaction size. A large number of wraps indicates that your extent size for your rollback segments are probably too small. Increase the size of your extents to reduce the number of wraps. You can look at the average transaction size in the same view to get the information on transaction size.

You Look At The Dba_rollback_segs View And See That You Have A Large Number Of Wraps Is This A Problem?

Answer»

A large NUMBER of wraps indicates that your extent size for your rollback segments are probably too SMALL. INCREASE the size of your extents to reduce the number of wraps. You can look at the average transaction size in the same view to GET the information on transaction size.

A large number of wraps indicates that your extent size for your rollback segments are probably too small. Increase the size of your extents to reduce the number of wraps. You can look at the average transaction size in the same view to get the information on transaction size.

Discussion

No Comment Found

Related InterviewSolutions

You See Multiple Extents In The Temporary Tablespace. Is This A Problem?
In A System With An Average Of 40 Concurrent Users You Get The Following From A Query On Rollback Extents: rollback Cur Extents r01 11 r02 8 r03 12 r04 9 system 4 you Have Room For Each To Grow By 20 More Extents Each. Is There A Problem? Should You Take Any Action?
You Look At The Dba_rollback_segs View And See That You Have A Large Number Of Wraps Is This A Problem?
You Look At The Dba_rollback_segs View And See That There Is A Large Number Of Shrinks And They Are Of Relatively Small Size, Is This A Problem? How Can It Be Fixed If It Is A Problem?
If You See The Value For Reloads Is High In The Estate Library Cache Report Is This A Matter For Concern?
If You See A Pin Hit Ratio Of Less Than 0.8 In The Estate Library Cache Report Is This A Problem? If So, How Do You Fix It?
What Can Cause A High Value For Recursive Calls? How Can This Be Fixed?
You See The Following On A Status Report: redo Log Space Requests 23 redo Log Space Wait Time 0 is This Something To Worry About? What If Redo Log Space Wait Time Is High? How Can You Fix This?
How Can You Tell If A Tablespace Has Excessive Fragmentation?
If A Tablespace Shows Excessive Fragmentation What Are Some Methods To Defragment The Tablespace? (7.1,7.2 And 7.3 Only)