You might experience a run-away process or OS problem. Is it possible to reboot?
03-21-2001, 12:24 PM
1) Check for smon timer waits, If u donot see any waits, then your smon is continiously active doing something.
Check for enteries in v$sort_Segment and also check for TS or ST locks.
2) If you have uniform extent size for ur tables then u can avoid the free extent coalescing by putting this event in your init.ora file:
event = "10269 trace name context forever"
03-21-2001, 12:28 PM
SMON does the following primary functions
1. Instance Recovery at startup
2. Coalescing space in tablespaces
3. Cleaning up temporary segments
i feel that uer problem lies in point no. 3., if uer application has generated a temporary segment very large and that needs to be cleaned after its use then SMON will have to consume excessive resources since the temporary segment has grown very large,
pls. check up the size of uer temp. segment and confirm , shall advice further
03-21-2001, 12:57 PM
SMON only frees temp extents when you shutdown the database
If you have no success rebooting Oracle you better try to reboot the server...
03-21-2001, 03:06 PM
via v$session and v$sql_area find what smon is executing and how frequently. If a lot of tablespaces where deleted during db life then this can cause slower processing.