Errors appeared in alert log file should send an email

Hi,
I have one requirement to do, as i am new dba, i dont know how to do this,
sendmail is configured on my unix machine, but dont know how to send the errors appeared in alert logfile should send an email to administrator.
daily, it has to check the errors in alert log file, if any errors occurs(ORA- errors or WARNING errors) should send an email to administrator.
please help me how to do it

Hi,
There are many methods for interrogating the alert log and sending e-mail. Here are my notes:
http://www.dba-oracle.com/t_alert_log_monitoring_errors.htm
- PL/SQL or Java with e-mail alert: http://www.dba-village.com/village/dvp_papers.PaperDetails?PaperIdA=2383
- Shell script - Database independent and on same level as alert log file and e-mail.
- OEM - Too inflexible for complex alert log analysis rules
- SQL against the alert log - You can define the alert log file as an external table and detect messages with SQL and then e-mail.
Because the alert log is a server side flat file and because e-mail is also at the OS-level, I like to use a server side scell script. It's also far more robust then OEM, especially when combining and evaluating multiple alert log events. Jon Emmons has great notes on this:
http://www.lifeaftercoffee.com/2007/12/04/when-to-use-shell-scripts/
If you are on Windows, see here:
http://www.dba-oracle.com/t_windows_alert_log_script.htm
For UNIX, Linux, Jon Emmons has a great alert log e-mail script.
Hope this helps . . . .
Donald K. Burleson
Oracle Press author

Similar Messages

"Error in the alert log file " - please help

Hi ALL,
I am getting following errors in the alert log frequently.
My database version is:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Productio
NLSRTL Version 10.2.0.1.0 - Production
Thu Aug 30 16:58:19 2007
Memory Notification: Library Cache Object loaded into SGA
Heap size 2172K exceeds notification threshold (2048K)
KGL object name :select object_name from all_objects where object_name='TOAD_PROFILER' and object_type='PACKAGE'
Thu Aug 30 17:09:36 2007
************************************************************************************

Additionally you can visit here:
Alert Error from trc files--Heap size 5236K exceeds notification threshold
geting error in alert log file
Adith

Error in the alert.log file

hi,
my database is down , when chk the alert log i found the below error
please help me
Sun Mar 8 20:06:01 2009
Errors in file /busdata/sp01/eur1/_lgi/oracle/vol1/admin/udump/sp01eur1_ora_3731494.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 5
Sun Mar 8 20:06:04 2009
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Sun Mar 8 20:06:04 2009
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled

madhukrishna wrote:
i am not authorised to start the databse or any servicesThen You have only one choice - please contact Your system administrator and he will investigate what happened, why and how to solve that.
We can't help or say what was wrong if You have no rights to do anything, even look at trace files.

Errors reported in alert log file regarding redo log files

Hi,
In my database i see the following entries regarding the redo log files frequently.
Thread 1 advanced to log sequence 88
Current log# 3 seq# 88 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\PELICAN\REDO03.LOG
Thread 1 advanced to log sequence 89
Current log# 1 seq# 89 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\PELICAN\REDO01.LOG
Thread 1 cannot allocate new log, sequence 90
Checkpoint not complete
I have 3 redo log files of 50MB each. My database is 10g.
What is the reason?
What do i need to do ?
Thanks.

Hi,
It is clearly stated that checkpoint is not complete. Thats why it could not allocate new sequence number to group 1.
We can understand that your redo log group size is insufficient. or increase the number of redo log groups.
Just test adding one more redo log group or test by increasing the size of redo log groups.

Job number from alert log file to information

Hello!
I have a question about job numbers in alert log file. Today one of our Oracle 10g R2 [10.2.0.4] RAC nodes crashed. After examining alert log file for one of the nodes I saw a lot of messages like:
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j002_28952.trc:
ORA-12012: error on auto execute of job *20627358*
ORA-12705: Cannot access NLS data files or invalid environment specified
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j001_11018.trc:
ORA-12012: error on auto execute of job *20627357*
ORA-12705: Cannot access NLS data files or invalid environment specified
Tue Jul 26 11:52:43 2011
Errors in file /u01/app/oracle/admin/zeme/bdump/zeme2_j000_9684.trc:
ORA-12012: error on auto execute of job *20627342*
ORA-12705: Cannot access NLS data files or invalid environment specified
After examining trc files I have found no further information about error except session ids.
My question is: how to find what job caused these messages to appear in alert log file.
How do I map number in alert log file to some "real" information (owner, statement executed, schedule)?
Marx.

Sorry for the delay
Try this to find the job :
select job, what from dba_jobs ;
How do I find NLS_LANG version?SQL> show parameter NLS_LANG
Do you mean ALTER SESSION inside a job?I meant anywhere, but your question is better.
ORA-12705 - Common Reasons and How to Resolve Them [ID 158654.1]
If OS is Windows lookout for NLS_LANG=NA in the registry
Is it possible you are doing this somewhere ?
ALTER SESSION SET NLS_DATE_FORMAT = 'RRRR-MM-DD\"T\"HH24:MI:SS';NLS database settings are superseded by NLS instance settings
SELECT * from NLS_SESSION_PARAMETERS;
These are the settings used for the current SQL session.
NLS_LANG could be set in a profile for example.
NLS_LANG=_AMERICA.WE8ISO8859P1 ( correct )
NLS_LANG=AMERICA.WE8ISO8859P1 ( Incorrect )
you need to set the "_" as separator.
Windows
set NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
Unix
export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
mseberg
Edited by: mseberg on Jul 28, 2011 3:51 PM
Edited by: mseberg on Jul 29, 2011 4:05 AM

ORA-1142 in alert log file

hello everybody,
I am getting the following ORA error in my Alert Log file.........
alter tablespace SYSTEM end backup
Sun Apr 13 01:42:58 2008
ORA-1142 signalled during: alter tablespace SYSTEM end backup..
what is this error??

The version of oracle i am running is
Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
PL/SQL Release 9.2.0.7.0 - Production
CORE 9.2.0.7.0 Production
TNS for Solaris: Version 9.2.0.7.0 - Production
NLSRTL Version 9.2.0.7.0 - Production........
Section of the Alert Log displaying the message................
Sun Apr 13 05:40:57 2008
Thread 1 advanced to log sequence 109947
Current log# 3 seq# 109947 mem# 0: /u09/oradata/inora/redo/redo03.log
Current log# 3 seq# 109947 mem# 1: /u10/oradata/inora/ctrl/redo03.log
Sun Apr 13 05:40:57 2008
ARCH: Evaluating archive log 2 thread 1 sequence 109946
ARCH: Beginning to archive log 2 thread 1 sequence 109946
Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109946.dbf'
Sun Apr 13 05:40:57 2008
ARC1: Evaluating archive log 2 thread 1 sequence 109946
ARC1: Unable to archive log 2 thread 1 sequence 109946
Log actively being archived by another process
Sun Apr 13 05:40:57 2008
ARCH: Completed archiving log 2 thread 1 sequence 109946
Sun Apr 13 05:40:59 2008
Thread 1 advanced to log sequence 109948
Current log# 1 seq# 109948 mem# 0: /u09/oradata/inora/redo/redo01.log
Current log# 1 seq# 109948 mem# 1: /u10/oradata/inora/ctrl/redo01.log
Sun Apr 13 05:40:59 2008
ARCH: Evaluating archive log 3 thread 1 sequence 109947
ARCH: Beginning to archive log 3 thread 1 sequence 109947
Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109947.dbf'
Sun Apr 13 05:40:59 2008
ARC0: Evaluating archive log 3 thread 1 sequence 109947
ARC0: Unable to archive log 3 thread 1 sequence 109947
Log actively being archived by another process
Sun Apr 13 05:40:59 2008
ARCH: Completed archiving log 3 thread 1 sequence 109947
Sun Apr 13 05:42:10 2008
alter tablespace SYSTEM end backup
Sun Apr 13 05:42:10 2008
ORA-1142 signalled during: alter tablespace SYSTEM end backup
Sun Apr 13 05:42:11 2008
Thread 1 advanced to log sequence 109949
Current log# 2 seq# 109949 mem# 0: /u10/oradata/inora/ctrl/redo02.log
Current log# 2 seq# 109949 mem# 1: /u09/oradata/inora/redo/redo02.log
Sun Apr 13 05:42:11 2008
ARCH: Evaluating archive log 1 thread 1 sequence 109948
ARCH: Beginning to archive log 1 thread 1 sequence 109948
Creating archive destination LOG_ARCHIVE_DEST_1: '/u08/oradata/inora/archive/inora_1_109948.dbf'
Sun Apr 13 05:42:11 2008
ARC1: Evaluating archive log 1 thread 1 sequence 109948
ARC1: Unable to archive log 1 thread 1 sequence 109948
Log actively being archived by another process

ORA.00600 Error in alert log file

Hi all,
I'm using Enterprise Linux Red hat 5 OS and Oracle version 10.2.0.1.0
I checked alert log file, yesterday i got this error,
* Errors in file /opt/oracle/admin/ssharp/udump/ssharp_ora_11162.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [0xB7F8F6B4], [], [], [], [], [], []
Fri Mar 11 19:44:51 2011
Memory Notification: Library Cache Object loaded into SGA
Heap size 3784K exceeds notification threshold (2048K) *
how to solve this issue?
thanks in advance

Hello,
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [0xB7F8F6B4], [], [], [], [], [], []For this kind of error you should open a Service Request to My Oracle Support and, send them all the information you can (Alert log, trace files, ...).
More over, as you are in *10.2.0.1*, you may apply the latest patchset to the Database (10.2.0.4 / 10.2.0.5). Sometime, ORA-00600 may be due to a Bug. So, perhaps, by chance, applying a Patch set can help to solve this kind of issue.
Anyway, first of all, contact the Support.
Hope this help.
Best regards,
Jean-Valentin

Errors in Alert log file

Hi,
I have encountered following errors in alrt log file, its strange to see FAST_START_MTTR_TARGET is out of valid and aksing to use another value and that value is changing every second, it should be in increasing order or it should be consistent. I think i have a serious problem, so anyone could help me out on this. I am getting this "FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead" error regurarly.
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24381 instead.
Wed Jan 16 23:40:34 2008
Completed checkpoint up to RBA [0x2aadb.2.10], SCN: 5473742880
Wed Jan 16 23:45:51 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 24017 instead.
Wed Jan 16 23:46:21 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23647 instead.
Wed Jan 16 23:46:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 23298 instead.
Wed Jan 16 23:47:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22906 instead.
Wed Jan 16 23:47:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22507 instead.
Wed Jan 16 23:48:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 22133 instead.
Wed Jan 16 23:48:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21786 instead.
Wed Jan 16 23:49:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21443 instead.
Wed Jan 16 23:49:52 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 21062 instead.
Wed Jan 16 23:50:22 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 20698 instead.
Wed Jan 16 23:53:53 2008
Incremental checkpoint up to RBA [0x2aadb.31b4.0], current log tail at RBA [0x2aadb.3e38.0]
Thu Jan 17 00:00:54 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 19582 instead.
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 16287 instead.
Thu Jan 17 00:34:01 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 15902 instead.
Thu Jan 17 00:34:31 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 14638 instead.
Thu Jan 17 00:35:01 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 13600 instead.
Thu Jan 17 00:35:31 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12773 instead.
Thu Jan 17 00:36:02 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12460 instead.
Thu Jan 17 00:36:32 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12338 instead.
Thu Jan 17 00:37:01 2008
Process P187 died, see its trace file
Thu Jan 17 00:37:02 2008
FAST_START_MTTR_TARGET 121 is out of the valid MTTR range, use 12248 instead.
Thu Jan 17 00:37:02 2008
Process P188 died, see its trace file
Thu Jan 17 00:37:03 2008
Process P189 died, see its trace file
Thu Jan 17 00:37:04 2008
Process P190 died, see its trace file
Thu Jan 17 00:37:16 2008
Process J000 died, see its trace file
Thu Jan 17 00:37:16 2008
kkjcre1p: unable to spawn jobq slave process
Thu Jan 17 00:37:16 2008
Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
Process J000 died, see its trace file
Thu Jan 17 00:37:22 2008
kkjcre1p: unable to spawn jobq slave process
Thu Jan 17 00:37:22 2008
Errors in file /oracle/BP3/saptrace/background/bp3_cjq0_4788.trc:
Thanks
Jafar

This parameter, FAST_START_MTTR_TARGET ranges from 0 to 3600 seconds. It is important to specify your oracle version, since a similar issue is reported for the 10gR1 release.
The solution for it would be to increase the value to the suggested one in the alert.log file, but it could be completely out of range from the valid values, so set it to zero and let the oracle instance calculate the value. You can check the output at the V$INSTANCE_RECOVERY view at the columns TARGET_MTTR, and ESTIMATED_MTTR prior to proceeding with modificaiton.
On the other hand, I suggest you to read this metalink note
Kkjcre1p: Unable To Spawn Jobq Slave Process, Error 1089
Doc ID: Note:344275.1
for the Kkjcre1p error message.
~ Madrid

RMAN success, but errors in alert.log file

My RMAN backup script runs well, but generates errors in alert.log file.
Here is the trace file contents:
/usr/lib/oracle/xe/app/oracle/admin/XE/udump/xe_ora_3990.trc
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
ORACLE_HOME = /usr/lib/oracle/xe/app/oracle/product/10.2.0/server
System name: Linux
Node name: plockton
Release: 2.6.18-128.2.1.el5
Version: #1 SMP Wed Jul 8 11:54:54 EDT 2009
Machine: i686
Instance name: XE
Redo thread mounted by this instance: 1
Oracle process number: 26
Unix process pid: 3990, image: oracle@plockton (TNS V1-V3)
*** 2009-07-23 23:05:01.835
*** ACTION NAME:(0000025 STARTED111) 2009-07-23 23:05:01.823
*** MODULE NAME:(backup full datafile) 2009-07-23 23:05:01.823
*** SERVICE NAME:(SYS$USERS) 2009-07-23 23:05:01.823
*** SESSION ID:(33.154) 2009-07-23 23:05:01.823
*** 2009-07-23 23:05:18.689
*** ACTION NAME:(0000045 STARTED111) 2009-07-23 23:05:18.689
*** MODULE NAME:(backup archivelog) 2009-07-23 23:05:18.689
Does anyone know why? Thanks.
Richard

I'm not sure if this will answer your question or not, but I believe these messages can likely be ignored.
I'm currently running 10.2.0.1.0 Enterprise Edition in pre-production (yes, I know I should apply the latest patchset and I plan to do so as soon as I get a development box allocated to me and can test it's impact). I see the same types of messages that you've reported with each of my regularly-scheduled backups:
a) The alert_<$SID>.log reports that there are errors in trace files:
Mon Aug 10 04:33:49 2009
Starting control autobackup
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Mon Aug 10 04:33:50 2009
Errors in file /opt/oracle/admin/blah/udump/blah_ora_32520.trc:
Control autobackup written to DISK device
handle '/backup/physical/BLAH/RMAN/cf_c-2740124895-20090810-00'
b) The .trc files, when you look at them contain no errors - only these "informational" messages:
*** 2009-08-10 04:33:50.781
*** ACTION NAME:(0000105 STARTED111) 2009-08-10 04:33:50.754
*** MODULE NAME:(backup archivelog) 2009-08-10 04:33:50.754
*** SERVICE NAME:(SYS$USERS) 2009-08-10 04:33:50.754
*** SESSION ID:(126.28030) 2009-08-10 04:33:50.754
c) I've verified that LOG_ARCHIVE_TRACE is set to 0:
SQL*Plus> show parameter log_archive_trace
NAME TYPE VALUE
log_archive_trace integer 0
As best I can discern from my own experience, these should just be ignored and I trust (read: "hope") they will simply go away once the latest patchset is applied. As for you running Oracle XE, a patchset is not an option, unfortunately.
V/R
-Eric

Configure Email through OEM when there is a error in alert log file

Hi,
I am using 10.2.0.4 on O/S RHEL5.0
I want to configure email facility through OEM so that whenever there is a error in alert log file i should receive an email.
Thanks and Regards
Amith

http://www.dba-oracle.com/oracle10g_tuning/t_oem_tuning.htm
Please read above link.
Regards
Girish Sharma

ORA- errors in alert log file

I wanted to know when the ORA- errors are reported into the alert.log file?
And which tye of errors are reported into it?
And if i wanted to log all the ORA-errors in the alert log then is there any setting for that?

You can find the type of errors reported in the link above.
Also, you maynot like to log ORA-00942: table or view does not exist, ORA-00904: : invalid identifier type of errors in alert.log - right? You may want to research at setting up events for generating trace files on specific error numbers you are looking at. That might resolve your problem - hth.

I am geting errors in my database alert log file ora-12012 and ora 44003

Hi all,
I am using oracle 10g ...10.2.0.1.0 and OS is solaris 10.......
i am geting these errors in my database alert log file last two days..i am not geting why it is coming?
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
and trace file is i got i am posting here please help any one is aware about this....
System name: SunOS
Node name: obrmzone1
Release: 5.10
Version: Generic_137111-06
Machine: sun4v
Instance name: ------
Redo thread mounted by this instance: 1
Oracle process number: 144
Unix process pid: 26874, image:--------- (J000)
*** ACTION NAME:(AUTO_SPACE_ADVISOR_JOB) 2011-06-10 22:00:49.372
*** MODULE NAME:(DBMS_SCHEDULER) 2011-06-10 22:00:49.372
*** SERVICE NAME:(SYS$USERS) 2011-06-10 22:00:49.372
*** SESSION ID:(110.7114) 2011-06-10 22:00:49.372
*** 2011-06-10 22:00:49.372
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
thank you in advance,
Dav

I just google with "ORA-44003: invalid SQL name" and found below link:
http://www.oracle-base.com/articles/10g/dbms_assert_10gR2.php
SIMPLE_SQL_NAME
The SIMPLE_SQL_NAME function checks the input string conforms to the basic characteristics of a simple SQL name:
The first character of the name is alphabetic.
The name only contains alphanumeric characters or the "_", "$", "#"
Quoted names must be enclosed by double quotes and may contain any characters, including quotes provided they are represented by two quotes in a row ("").
The function ignores leading and trailing white spaces are ignored
The length of the input string is not validated.

How to check particular error in alert log file

Hi all,
How to check particular error in alert log file,for supose if i get error in batabase yesterday 4 pm & today i want to check alert log file to get basic idea..it might be a big file so how to check that particular error..
Thanks & regards,
Eswar..

What's your oracle version?
If you are in 11g you can use adrci tool
1- set homes diag/rdbms/orawiss/ORAWISS/ : the rdbms home
2- show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term : to find all the ORA-% errors in the alert file
3- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term : to find all the ORA-% errors in the alert file during the last 51 days,
4- show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-1/24 " -term : to find all the ORA-% errors in the alert file during the last hour,
5- show alert -P "MESSAGE_TEXT LIKE '%ORA-12012%' and originating_timestamp > systimestamp-1/24 " -term : to find the particular ORA-12012 error in the alert file during the last hour,
Example:
[oracle@wissem wissem]$ adrci
ADRCI: Release 11.2.0.1.0 - Production on Wed May 4 10:24:54 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
ADR base = "/home/oracle/app/oracle"
adrci> set homes diag/rdbms/orawiss/ORAWISS/
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-'" -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%'" -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
2010-12-11 19:45:41.289000 +01:00
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/home/oracle/app/oracle/oradata/ORAWISS/system01.dbf'
ORA-1547 signalled during: ALTER DATABASE RECOVER database until time '2011-01-21:10:48:00' ...
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
ORA-12012: error on auto execute of job 29
ORA-01435: user does not exist
2011-03-15 11:39:37.571000 +01:00
opiodr aborting process unknown ospid (31042) as a result of ORA-609
2011-03-15 12:04:15.111000 +01:00
opiodr aborting process unknown ospid (3509) as a result of ORA-609
adrci>
adrci> show alert -P "MESSAGE_TEXT LIKE '%ORA-%' and originating_timestamp > systimestamp-51 " -term
ADR Home = /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS:
2011-03-15 10:19:45.316000 +01:00
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j006_5536.trc:
ORA-12012: error on auto execute of job 26
ORA-01435: user does not exist
Errors in file /home/oracle/app/oracle/diag/rdbms/orawiss/ORAWISS/trace/ORAWISS_j000_5692.trc:
ORA-12012: error on auto execute of job 29
ORA-01435: user does not exist
2011-03-15 11:39:37.571000 +01:00
opiodr aborting process unknown ospid (31042) as a result of ORA-609
2011-03-15 12:04:15.111000 +01:00
opiodr aborting process unknown ospid (3509) as a result of ORA-609
adrci>

Block corruption error keep on repeating in alert log file

Hi,
Oracle version : 9.2.0.8.0
os : sun soalris
error in alert log file:
Errors in file /u01/app/oracle/admin/qtrain/bdump/qtrain_smon_24925.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-01578: ORACLE data block corrupted (file # 1, block # 19750)
ORA-01110: data file 1: '/u01/app/oracle/admin/qtrain/dbfiles/system.dbf'system datafile is restored from backup still the error is logged in alert log file
Inputs are appreciated.
Thanks
Prakash

Hi,
Thanks for the inputs
OWNER                          SEGMENT_NAME                                                                      PARTITION_NAME                 SEGMENT_TYPE       TABLESPACE_NAME                 EXTENT_ID    FILE_ID   BLOCK_ID      BYTES     BLOCKS RELATIVE_FNO
SYS                            SMON_SCN_TO_TIME                                                                                                 CLUSTER            SYSTEM                                  1          1      19749      16384          1            1
SYS                            SMON_SCN_TO_TIME                                                                                                 CLUSTER            SYSTEM                                  2          1      19750      32768          2            1Thanks
Prakash

Receiving Alerts on ORA- error in Alert Log File

Hi,
I am using 10.2.0.5 OEM grid control and same versioned agent on my database servers. I have configured the alert email notification if there is any ORA- error message in my alert log file. The metric i selcted for this is "Generic Alert Log Error Status". In notification email, i see only the message that there is generic error message in the alert log file. Is there any way to set this notification so that i receive the exact ORA- error message in my alert notification email if there is any kind of ORA- error found in my alert log file?
Thanks
Salman

Please look into the Metalink Note: 458605.1
Subject: Receiving "Clear" Notifications Unexpectedly for 'Generic Alert Log Error Status' Metric

Errors appeared in alert log file should send an email

Similar Messages

Maybe you are looking for