Oracle's alert.log
alert.log chronologically records messages and errors arising from the daily database operation. Also, there are pointers to
trace files and dump files.
These messages include
Create
, alter
and drop
SQL statements on databases, tablespaces and rollback segments. alert.log is a text file that can be opened with any text editor. The directory where it is found can be determined by the
background_dump_dest initialization parameter:
select value from v$parameter where name = 'background_dump_dest
';
If the background_dump_dest parameter is not specified, Oracle will write the alert.log into the
$ORACLE_HOME /RDBMS/trace
directory. Here's a shell/
awk script to
analyze alert logs .
Common messages in the alert log ARCx: Media recovery disabled
This message will be written into the alert.log if the
arch process is started with the database being in
noarchive log mode .
It's unfortunately possible for ARCH to be sitting around doing nothing apart from just taking up memory when the database is in noarchive log mode.
The archiver can be stopped dynamically:
alter system archive log stop .
Ignoring SIGALARM
Such a message is written into the alert log when a process that waited for a
semaphore gets the semaphore shortly befor the
timeout expires and doesn't have the time to switch the timeout mechanism off.
Thread 1 cannot allocate new log, sequence 1558 Checkpoint not complete
This error message is written into the alert.log if a
checkpoint cannot write all dirty
db blocks to the
online redo log .
Usually, this message is a sign that the size of the redo logs is to small or that there should be more of them.
Rotating the alert logs
Within Oracle, it is perfectly possible to delete, or rename, the alert.log, if desired (for example, if it reaches a certain size). Oracle simply recreates a new alert.log the next time it writes to it.
Linux (and other Unixes?) has an utility called
logrotate to automate that task.
Writing own messages into the alert log
The undocumented procedure kdswrt in
dbms_system allows to write own messages in the alert log.
begin
sys.dbms_system
.ksdwrt(2, 'My own message');
end;
/
Reading the alert log through an external table
Here is a procedure which creates an
external table that can be used to read the alert.log.
There is also a
script to read the alert log which doesn't require a procedure such as the previous link.
이 내용에 흥미가 있습니까?
현재 기사가 여러분의 문제를 해결하지 못하는 경우 AI 엔진은 머신러닝 분석(스마트 모델이 방금 만들어져 부정확한 경우가 있을 수 있음)을 통해 가장 유사한 기사를 추천합니다:
Exception in thread main java.lang. NoClassDefFoundError 오류 해결 방법즉,/home/hadoop/jarfile) 시스템은 Hello World 패키지 아래의class라는 클래스 파일을 실행하고 있다고 오인하여 시스템의 CLASSPATH 아래 (일반적으로 현재 디렉터리를 포함) Hell...
텍스트를 자유롭게 공유하거나 복사할 수 있습니다.하지만 이 문서의 URL은 참조 URL로 남겨 두십시오.
CC BY-SA 2.5, CC BY-SA 3.0 및 CC BY-SA 4.0에 따라 라이센스가 부여됩니다.