| capture users & statements causing archive log full [message #178473] |
Wed, 21 June 2006 04:21  |
jasbosky
Messages: 1
Registered: June 2006
|
Junior Member |
|
|
Hi,
pretty new to oracle and i encountered archive log full messages very often in the db alert logs recently. The database will hang in the middle of the night and i have to come in early to compress and clear the log files before users start calling in to complain on slowness. There are alot of application cron jobs running and im not sure how to identify the 'offending' users. The growth in the 10G archive log directory is very rapid. Within 1 hour, the mount point will be full.
Will like to know if there are any v$ views to capture the users,statements,local/remote causing the archive log to grow so rapidly? Perhaps write a script to run when unix threshold of archive log mount point reached 90%.
And what are the reasons that cause archive log mount point to grow so fast and how to prevent/minimise this from happening.
Please help..thanks.
|
|
|
|
| Re: capture users & statements causing archive log full [message #178505 is a reply to message #178473] |
Wed, 21 June 2006 05:09  |
orausern
Messages: 826
Registered: December 2005
|
Senior Member |
|
|
one general pointer could be: try to estimate how much approx. amount of redo logs (in mb/gb etc) are generated every day, and have at least twice that amound as the free space in archive dest. You should explore if you can change ur present archive destination to another one , which has the required free space.
It may not be practical to ask users to do less activity , just because archive logs are getting filled up. That way, if no one does anything, you will never have it full..so do not explore on the front of finding users who do too much work and trying to restrict them, rather, to provide more space so they may do whatever they want to.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
