|
|
Cooperative Extension Service |
|
 |
||
|
|
||
|
Agricultural
Experiment Station |
||
 |
|
|
If you suddenly find that your archive logs directory is filling up with archives being generated every minute or so, you may be able to find the culprit document or user ID or process, depending on what fields are being changed, by scanning the latest archivelog file for the strings that are being included most often in the changes being written to that archive log.
The following unix command line example extracts the strings from an archivelog file, sorts the resulting string lines, counts the unique strings, finds the largest occurrence numbers (there is a blank after the first "0-9"), and sorts those occurrences by the string counts (the "ls" line shows the latest archivelog file at the end of it's listing in the "cd" line's archive log directory). You can then look through the resulting sorted counts and strings to see if there is any indication as to what is causing the problem that is filling up your logs. (Substitute your archive log directory and resulting latest archivelog file name that you want to check.)
cd /u01/oradata/PROD/archivelogs
ls -ltr
strings arch_PROD_00072.arc | sort | uniq -c | grep '^[0-9 ][0-9]' | sort -n
This Page was Last Updated on 06/04/07
You Are Visitor Number |
|
|
© 2006 |
|
|
University of Arkansas • Division of Agriculture |
Mission
•
Disclaimer
•
EEO
•
|
