Summary
Symptom
Oracle alert log file has grown to an enourmous size
Other terms
alert_SID.log
Reason and Prerequisites
The alert log file of the database is written chronologically. Data is always appended at the end so it will grow large fast.
The alert log file should be renamed on a regular basis, as a large alert file occupies unnecessary disk space, can slow down OS write performance to the file.
SolutionThe alert log file should be renamed on a regular basis, as a large alert file occupies unnecessary disk space, can slow down OS write performance to the file.
Find the Alert log location by checking the parameter BACKGROUND_DUMP_DEST
On a SAP environment by default it is located on the directory:
[UNIX] /oracle/<SID>/saptrace/background
[WIN] <drive>:\oracle\<SID>\saptrace\background
You can rename the Alert log while the Oracle instance is up. The Alert log will be recreated when the next alert entry is written.
It is recommended to keep an historical for troubleshooting purposes.
On a SAP environment by default it is located on the directory:
[UNIX] /oracle/<SID>/saptrace/background
[WIN] <drive>:\oracle\<SID>\saptrace\background
You can rename the Alert log while the Oracle instance is up. The Alert log will be recreated when the next alert entry is written.
It is recommended to keep an historical for troubleshooting purposes.
Header Data
| Release Status: | Released for Customer |
| Released on: | 29.11.2004 12:33:33 |
| Master Language: | English |
| Priority: | Recommendations/additional info |
| Category: | Help for error analysis |
| Primary Component: | BC-DB-ORA Oracle |
Affected Releases
Release-Independent
Related Notes
| 592393 - FAQ: Oracle | |||
| 540434 - FAQ: Crucial Information for Oracle DB Administration |
No comments:
Post a Comment