Are you looking for details about monitoring Errors in the Alert log? Would you also like to know about ORA errors such as ORA-7445 , ORA-1653 ,ORA-1650 etc? If so, then you reached the right place. In this article, we will understand monitoring Errors in the Alert logs.
A) What are Alert logs?
The important information about error messages and exceptions which occurs during various operation database is captured in the log file called Alert logs.
Each Oracle database for windows instance has one alert log.
B) What is the location of Alert logs?
We set the path for DIAGNOSTIC_DEST initialization parameter. At this path location, the alert log file is created. Normally, the alert file name is alert _SID.log
C) Database crash errors
These errors are associated with an error that can be severe enough to crash an oracle instance. To analyze the oracle instance crash issue we need to capture a trace file or a core dump file and sent it to oracle technical support.
D) ORA - 600 Errors
The ORA-600 will not crash the oracle database. However, it may produce a core dump or trace file -
Example of trace file -
Errors in file /ora/home/dba/oracle/product/rdbms/log ora_ 123.trc
ORA-00600= internal error code , arguments : [12700],[12345],[61],[ ],[ ]....
E) ORA-1578
If a data block is read that appears corrupt in such case ORA-1578 is returned. This error message provides details of the file and block number.
e.g.
ORA-D1578 ORACLE data block corrupted (file#xyz, block#01)
F) ORA-1650
It is an error message related to the rollback segment. The error message 'ORA-1650 cannot extend rollback segment ' is produced when the rollback segment has become full. The oracle instance will not crash but the task will be terminated.
e.g. ORA-1650 is unable to extend rollback segment PQR by 64000 in tablespace ROLLBACK.
Based on the above critical error messages we can build the monitoring system.
Learn more about oracle here -
No comments:
Post a Comment
Please do not enter any spam link in the comment box.