Prevent message to go to the alert.log file

Hi
How can I prevent any message (for exm. SHUTDOWN IMMEDIATE) to be written to alert.log file? Is it possible?
Thanks
John

Of course this can be done with some scripting, but alot of work and totaly worthless, why dont you want it to be shown in your alert log?
if shutdown immediate present
then cache alert log, rewrite it to new alert log without the text shutdown immediate, but as i said earlier, useless. :)

Similar Messages

Ora-07445 reported in the alert log file

Hi all,
We are using the following platform:-
OS: Solaris Operating System (SPARC 32-bit)
Oracle Server - Enterprise Edition / Product Version: 9.2.0.5.0
We encountered the following problem:-
There is Ora-07445 reported in the alert log file.
"ORA-07445: exception encountered: core dump [kgghash()+308] [SIGSEGV] [Address not mapped to object] [0x3222
000] [] []reported in the database."
These errors are signaled in more than 3 independent, unexplained, occurrences every day.
When this error occurred while User was accessing the application system, by right the case will be shown on the system, but they were no case found.
alert log are as below:-
Fri Jul 27 09:12:30 2007
Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27371.trc:
ORA-07445: exception encountered: core dump [kgghash()+340] [SIGSEGV] [Address not mapped to object] [0x3184000] [] []
Fri Jul 27 09:22:10 2007
Thread 1 advanced to log sequence 10730
Current log# 2 seq# 10730 mem# 0: /disc3/oracle9205/RFDB/RDO/logRFDB2a.rdo
Current log# 2 seq# 10730 mem# 1: /disc3/oracle9205/RFDB/RDO/logRFDB2b.rdo
Fri Jul 27 09:29:26 2007
Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27372.trc:
ORA-07445: exception encountered: core dump [kgghash()+296] [SIGSEGV] [Address not mapped to object] [0x3182000] [] []
The applications have encountered ora-3113 after a short period of time followed by ora-3114.
application log:-
RF0120-1 2007-Jul-27 09:46:57] Load m[RF0120-1 2007-Jul-27 09:29:30] SQLCODE: -3113
[RF0120-1 2007-Jul-27 09:29:30] Error Code -4105 returning from get score pan no.
[RF0120-1 2007-Jul-27 09:29:30] Message type :120
[RF0120-1 2007-Jul-27 09:29:30] Primary Account Number(PAN) DE0
02 :5440640155262702
[RF0120-1 2007-Jul-27 09:29:30] Processing code DE003 :003000
[RF0120-1 2007-Jul-27 09:29:30] Transaction amount DE004 :000000000001
[RF0120-1 2007-Jul-27 09:29:30] Settlement amount DE005 :000000000000
[RF0120-1 2007-Jul-27 09:29:30] Transmission Date and time
DE007 :0727092717
[RF0120-1 2007-Jul-27 09:29:30] Settlement conversion rate DE009 :60263158
[RF0120-1 2007-Jul-27 09:29:30] System trace audit no. DE011 :754710
[RF0120-1 2007-Jul-27 09:29:30] Local transaction time DE012 :092717
[RF0120-1 2007-Jul-27 09:29:30] Local transaction date DE013 :0727
[RF0120-1 2007-Jul-27 09:29:30] Expiration date D
E014 :0712
[RF0120-1 2007-Jul-27 09:29:30] Settlement date DE015 :0727
[RF0120-1 2007-Jul-27 09:29:30] Merchant type DE018 :5311
[RF0120-1 2007-Jul-27 09:29:30] Point-of-service(POS) entry code DE022 :051
[RF0120-1 2007-Jul-27 09:29:30] Acquiring inst. ID code DE032 :001912
[RF0120-1 2007-Jul-27 09:29:30] Forwarding Inst. ID code DE033 :001912
[RF0120-1 2007-Jul-27 09:29:30] Retrieval ref. no.
DE037 :754710356390
[RF0120-1 2007-Jul-27 09:29:30] Autholization ID response DE038 :356390
[RF0120-1 2007-Jul-27 09:29:30] Response code DE039 :00
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor terminal ID DE041 :19306002
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor ID code DE042 :000001106
020132
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor Name/Location
What could have caused the above mentioned errors i.e Ora-07445 ; ora-3113 / ora-3114? How to resolve the problem.
Please help .
Thanks.

i am also facing the same some time in ora 9.2.0.6 on Sun OS 9 SPARC 64-bits
Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6076.trc:
ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
Thu Aug 30 08:52:39 2007
Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6078.trc:
ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
Thu Aug 30 09:41:49 2007

Will the informations be recorded in the alert.log file? -----No.168

will the informations about the loss of a temporary file be recorded in the alert.log file?

Yes, because whe your database starts needs to "mount" a tablespace with temporary files (case of tablespace "TEMP"). But don't worry with a loss of this tablespace because doesn't contain nothing when database starts.

How to be notified for all ORA- Errors recorded in the alert.log file

based on Note:405396.1, I Changed the Matches Warning from the default value ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] to ORA-* in order to receive an warning alert for all ORA- errors.
but I just recieved the alert like the following:
Metric=Generic Alert Log Error
Time/Line Number=Mon Feb 25 23:52:21 2008/21234
Timestamp=Feb 26, 2008 12:06:03 AM EST
Severity=Warning
Message=ORA-error stack (1654, 1654, 1654) logged in /opt/oracle/admin/PRD/bdump/alert_PRD.log.
Notification Rule Name=Alert Log Error
Notification Rule Owner=SYSMAN
as you can see, the message only indicate the ORA-1654, nothing else.
How to set in 10g grid control to get the details alert that in the alert log like:
"ORA-1654: unable to extend index ADM.RC_BP_STATUS by 1024 in tablespace PSINDEX"
I can't believe Oracle 10g Grid control only provide the ORA- number without details

Go to your database target.
On the home tab, on the left hand side under Diagnostic Summary, you'll see a clickable date link next to where it says 'Alert Log'. Click on that.
next click on Generic Alert Log Error Monitoring Configuration (its at the bottom)
In the alert thresholds put:
ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]
I believe that will pick anything up but experiment, its only perl.
If you want to test this use the DBMS_System.ksdwrt package but I would advise you only do so on a test database. If you've never heard of it, google it. Its a way of writing to your alert log.
Make sure you have your emails sent to long format as well.

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.

"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

How to read trace files alerted in the alert.log file

Hello,
My alert.log file indicated multiple trace files to review. How to read these trace files to understand the cause of errors. Do I open the trace files with vi and do a search for 'ORA-' error. Are there tools to read and understand trace files. Thank you.

It depends what kind of trace file it is.
You can use vi or other text editing tool to open the trace file. The trace file usually provides more detailed information when you have ORA- errors in alert.log. It's also very helpful for Oracle support when troubleshooting.

ORA-00316 in the alert log file

Thu Aug 21 17:23:05 2008
Errors in file /ora_dump/CONCILIA/bdump/concilia_arc1_205172.trc:
ORA-00316: log 3 of thread 1, type 0 in header is not log file
ORA-00312: online log 3 thread 1: '/ora_data04/CONCILIA/redo01.log'
Thu Aug 21 17:23:05 2008
Errors in file /ora_dump/CONCILIA/bdump/concilia_arc1_205172.trc:
ORA-00316: log 3 of thread 1, type 0 in header is not log file
ORA-00312: online log 3 thread 1: '/ora_data04/CONCILIA/redo01.log'
$

It looks like your redo log might be corrupted.
Check the content of trc file and work with Oracle support.
00316, 00000, "log %s of thread %s, type %s in header is not log file"
// *Cause: The online log is corrupted or is an old version.
// *Action: Find and install correct version of log or reset logs.

Error at the time of startup command in the alert log file

replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=16, OS id=1354
Thu May 10 16:31:12 2007
Completed: alter database open
Thu May 10 16:37:05 2007
Shutting down archive processes
Thu May 10 16:37:10 2007
ARCH shutting down
ARC2: Archival stopped
Fri May 11 10:31:16 2007
Starting ORACLE instance (normal)
Fri May 11 10:31:16 2007
System parameter db_block_buffers enabled without VLM on.
Cannot determine all dependent dynamic libraries for /proc/self/exe
Unable to find dynamic library libocr10.so in search paths
RPATH = /ade/aime1_build2101/oracle/has/lib/:/ade/aime1_build2101/oracle/lib/:/ade/aime1_build2101/oracle/has/lib/:
LD_LIBRARY_PATH is not set!
The default library directories are /lib and /usr/lib
Unable to find dynamic library libocrb10.so in search paths
Unable to find dynamic library libocrutl10.so in search paths
Unable to find dynamic library libocrutl10.so in search paths
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 50
shared_pool_size = 83886080
control_files = /disk1/oradata/bhrigus/cont.ctl
db_block_buffers = 512
log_archive_dest = /disk1/oradata/bhrigus/arch
log_buffer = 2927616
log_checkpoint_interval = 10000
db_files = 80
db_file_multiblock_read_count= 8
undo_management = AUTO
undo_tablespace = UNDOTBS
undo_retention = 900
global_names = TRUE
instance_name = bhrigus
parallel_max_servers = 5
background_dump_dest = /disk1/oradata/bhrigus/bdump
user_dump_dest = /disk1/oradata/bhrigus/udump
max_dump_file_size = 10240
core_dump_dest = /disk1/oradata/bhrigus/cdump
db_name = srinivas
PMON started with pid=2, OS id=1438
MMAN started with pid=4, OS id=1442
PSP0 started with pid=3, OS id=1440
DBW0 started with pid=5, OS id=1444
LGWR started with pid=6, OS id=1446
CKPT started with pid=7, OS id=1448
SMON started with pid=8, OS id=1450
RECO started with pid=9, OS id=1452
MMON started with pid=10, OS id=1454
MMNL started with pid=11, OS id=1456
Fri May 11 10:31:21 2007
ALTER DATABASE MOUNT
Fri May 11 10:31:25 2007
Setting recovery target incarnation to 2
Fri May 11 10:31:25 2007
Successful mount of redo thread 1, with mount id 2799846073
Fri May 11 10:31:25 2007
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Fri May 11 10:31:25 2007
ALTER DATABASE OPEN
Fri May 11 10:31:25 2007
Beginning crash recovery of 1 threads
Fri May 11 10:31:25 2007
Started redo scan
Fri May 11 10:31:26 2007
Completed redo scan
1334 redo blocks read, 56 data blocks need recovery
Fri May 11 10:31:26 2007
Started redo application at
Thread 1: logseq 204, block 4933
Fri May 11 10:31:26 2007
Recovery of Online Redo Log: Thread 1 Group 2 Seq 204 Reading mem 0
Mem# 0 errs 0: /disk1/oradata/bhrigus/redolog2.log
Fri May 11 10:31:26 2007
Completed redo application
Fri May 11 10:31:26 2007
Completed crash recovery at
Thread 1: logseq 204, block 6267, scn 837030
56 data blocks read, 56 data blocks written, 1334 redo blocks read
Fri May 11 10:31:26 2007
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=13, OS id=1460
ARC1 started with pid=14, OS id=1462
Fri May 11 10:31:26 2007
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Thread 1 advanced to log sequence 205
Thread 1 opened at log sequence 205
Current log# 1 seq# 205 mem# 0: /disk1/oradata/bhrigus/redolog1.log
Successful open of redo thread 1
Fri May 11 10:31:26 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri May 11 10:31:26 2007
SMON: enabling cache recovery
Fri May 11 10:31:26 2007
ARC0: STARTING ARCH PROCESSES
Fri May 11 10:31:26 2007
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Fri May 11 10:31:26 2007
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC0: Becoming the heartbeat ARCH
ARC2 started with pid=15, OS id=1464
Fri May 11 10:31:29 2007
Successfully onlined Undo Tablespace 1.
Fri May 11 10:31:29 2007
SMON: enabling tx recovery
Fri May 11 10:31:29 2007
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
been restored. It may be necessary to add files to these
tablespaces. That can be done using the SQL statement:
ALTER TABLESPACE <tablespace_name> ADD TEMPFILE
Alternatively, if these temporary tablespaces are no longer
needed, then they can be dropped.
Empty temporary tablespace: TEMP
Database Characterset is US7ASCII
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=16, OS id=1466
Fri May 11 10:31:33 2007
Completed: ALTER DATABASE OPEN
Fri May 11 10:31:36 2007
Starting background process CJQ0
CJQ0 started with pid=18, OS id=1472

Error message is explicit and straight forward:
Fri May 11 10:31:29 2007
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
been restored. It may be necessary to add files to these
tablespaces. That can be done using the SQL statement:
ALTER TABLESPACE <tablespace_name> ADD TEMPFILE
Alternatively, if these temporary tablespaces are no longer
needed, then they can be dropped.
Empty temporary tablespace: TEMP
*********************************************************************Database will startup, but by the time you try to create a temporary segment through an order by requiring temporary segments, an error will show up.
Just add datafiles to your temporary tablespace:
ALTER TABLESPACE TEMP ADD TEMPFILE[i] 'yourTempPath/yourTempFileName.dbf' SIZE nnM autoextend on;
Replace the italics with suitable parameter values.

Message in alert log file during the startup of the DB

Hi,
i have two instances, i have the same warning in the alert log file during the startup of the DB:
Oracle instance running on a system with low open file descriptor limit.
Tune your system to increase this limit to avoid severe performance degradation.
The db_files parameter was at 1024 for the two instances, i have set it to 300 for the first instance and 550 for second, the message for the first instance was droped(it's ok), but the message was there in the alert log for the second instance.
The two instance are on the same machine.
The number of the open file limit on the linux machine is equal to 1024.
I have shutdown the first instance (with db_files=300) the problem persits for the second instance (with db_files=550).
My question is how to determinate the right value of db_files parameter to avoid this message.
Regards.
Message was edited by:
learn

Increase the max number of open file on Linux or decrease db_files.
f the OS limit is 1024 db_files would have to be >= 472 for the message to be printed. t is printed if an instance is configured to access more datafiles than the OS-specific limit on the number of files that can be open in a single process. In this case the server will re-cycle the file descriptors.
Vadim Bobrov
Oracle Database Tools
http://www.fourthelephant.com

Purging the ALERT LOG

Hi,
I am using RDBMS : 9.2.0.6.0 on AIX 5.3 platform.
I want to purge my alter log file as it is never been purged and is almost contains the entry of past 1 year.
Can you please provide me the way to do it?
Thanks
Shivank

If there is no alert log the database will create another one, so you can remove/delete the alert log file.
If you don't want to delete the alert log file. You can rename it while the database is down. So it will create and use a new alert log file.
You can also empty the file as follows;
cp -p alert.log alert.log.date (backing up the alert log file)
echo ""> alert.log (empty the alert log file)
You can also use as follows;
tail -3000 alert_test01.log > alert_test01.log_new (this will take last 3000 lines).
Additionally specifying your O/S would be helpful.
Adith
Thanks
Message was edited by:
Adith

Hi We got the below alert but its not reported in the alert.log

The following SQL error occurred ORA-00054:resource busy had accquire with NOWAIT specified but its not reported in the alert log file
Regards

Hi,
Error: ORA-00054
Text: resource busy and acquire with NOWAIT specified or timeout expired
=========================================================================
Cause: Resource interested is busy or the timeout specified by DDL_LOCK_TIMEOUT has expired
Action: Retry the command with a higher DDL_LOCK_TIMEOUT if desired
Check this what could be in alert log file :Monitoring Errors and Alerts
HTH

How to open the alert logs

Hi Team,
I am doing database Refreshment. I want to monitor the alert logs.
Please suggest me, How to open the alert logs. Working on unix server.
Thanks & Regards,

if its 10g then go to bdump directory
you can either do tail -f <alert_log_name>
or vi <alert_log_name>
if 11g then you want should go to
$ORACLE_HOME/diag/$ORACLE_SID
the alert log file is in XML format as well as a text file. The default location of both these files is the new ADR home or Automatic Diagnostic Respository. The ADR is set by using the DIAGNOSTIC_DEST initialization parameter. The location of an ADR home is ADR_BASE/diag/product_type/product_id/instance_id. If the environment variable ORACLE_BASE is not set then DIAGNOSTIC_DEST is set to ORACLE_HOME/log
there are different directories for different types of alert log files
alert - The XML formatted alertlog
trace - text alert log

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

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

Prevent message to go to the alert.log file

Similar Messages

Maybe you are looking for