Dba_outstanding_alerts

Hi,
Database has been initially created with FLASHBACK MODE on, then turned off. There was an outstanding alert related to recovery area which is not cleared. The problem should have been the recovery area is cleared with OS commands instead of RMAN. Now the database uses no Flashback, no recovery_file_dest set however the alert is not cleared. How to clear this alert from the database.
SQL>select FLASHBACK_ON from v$database;
FLASHBACK_ON
NO
SQL>show parameter db_reco
NAME TYPE VALUE
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
SQL>select REASON_ID,OBJECT_NAME,OBJECT_TYPE,REASON,TIME_SUGGESTED,CREATION_TIME,ADVISOR_NAME,METRIC_VALUE from dba_outstanding_alerts
2 /
REASON_ID OBJECT_NAME OBJECT_TYPE REASON TIME_SUGGESTED CREATION_TIME ADVISOR_NAME METRIC_VALUE
123 RECOVERY AREA RECOVERY AREA db_recovery_file_dest_size of 2147483648 bytes is 22-MAR-06 12.14.09.083534 PM -05:00 22-MAR-06 12.11.06.324343 PM -05:00 97
97.15% used and has 61112320 remaining bytes avail
able.
Grid control displays this alert as critical Need to clear this from database.
Metric Recovery Area Free Space (%)
Recovery Area RECOVERY AREA
Severity Critical
Timestamp May 19, 2007 1:20:27 AM
Administrator <SYSTEM>
Message db_recovery_file_dest_size of 2147483648 bytes is 97.15% used and has 61112320 remaining bytes available.
Thanks in advance

Can anyone help clearing alerts like above mentioned which are not relevent any more from dba_outstanding_alerts.

Similar Messages

Dba_outstanding_alerts-addm

can any one tell me ADDM. I have got message from dba_outstanding_alerts.
EVENT_CLASS Warning 5
Metrics "Database Time Spent Waiting (%)" is at 60.98381 for event class "Other"
Run ADDM to get more performance analysis about your system.
please clarify this alert.

dbaforu,
I presume you have not read the documentation that i have pointed out;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/diagnsis.htm
+6.2.4.1 Running ADDM Using addmrpt.sql+
To invoke ADDM analysis for the scenario previously described, you can simply run the addmrpt.sql script at the SQL prompt:
+@$ORACLE_HOME/rdbms/admin/addmrpt.sql+
When running the addmrpt.sql report to analyze the specific time period in the example scenario, you need to:
+1.+
Identify the last snapshot that was taken before or at 7 P.M. and the first snapshot that was taken after or at 9 P.M. of the previous night from the list of recent snapshots that the report initially displays. The output is similar to the following:
Listing the last 3 days of Completed Snapshots
+...+
Snap
Instance     DB Name        Snap Id    Snap Started    Level
main         MAIN               136 20 Oct 2003 18:30      1
+137 20 Oct 2003 19:00 1+
+138 20 Oct 2003 19:30 1+
+139 20 Oct 2003 20:00 1+
+140 20 Oct 2003 20:30 1+
+141 20 Oct 2003 21:00 1+
+142 20 Oct 2003 21:30 1+
+2.+
Provide the snapshot Id closest to 7 P.M. when prompted for the beginning snapshot and the 9 P.M. snapshot Id when prompted for the ending snapshot.
Enter value for begin_snap: 137
Begin Snapshot Id specified: 137
Enter value for end_snap: 141
End   Snapshot Id specified: 141
+3.+
Enter a report name or accept the default name when prompted to specify the report name.
Enter value for report_name:
Using the report name addmrpt_1_137_145.txt
Running the ADDM analysis on the specified pair of snapshots ...
Generating the ADDM report for this analysis ...
After the report name is specified, ADDM analysis over the specific time frame is performed. At the end of the analysis, the SQL script displays the textual ADDM report of the analysis. You can review the report to find the top performance issues affecting the database and possible ways to solve those issues.
Instructions for running the report addmrpt.sql in a non-interactive mode can be found at the beginning of the $ORACLE_HOME/rdbms/admin/addmrpt.sql file.
Ogan

ENterprise Manager SNMP Traps

Hi all,
I have configured the Database Control (not Grid Control) to send SNMP alert in our monitoring system.
I have added notification rules per target (Instance, Cluster, Database, Host, ASM, Listener). For Each notification rule I have added the metrics and specified the SNMP method.
Now, testing the SNMP alert for Tablespace Space Used (%) , I have created a small tablespace datafile and fill it with data, as you can see below.
The issue is that the tablespace alert is not showing in the monitoring system where a previous test I have made to shutdown the database shows the database down alert on the monitoring system. How can I troubleshoot the issue?
Thank you
SQL> SELECT REASON, OBJECT_NAME, OWNER from DBA_OUTSTANDING_ALERTS;
REASON
OBJECT_NAME
OWNER
Tablespace [TSPACE_TEST] is [100 percent] full
TSPACE_TEST

11g wrote:
Look at the log files at location $ORACLE_HOME/sysman/log for error messages..There is no recent messages in the log file. Last update 04th of August,
[oracle@db01 admin]$ cd $ORACLE_HOME/sysman/log
[oracle@db01 log]$ ls -rtl
total 288
-rw-r--r-- 1 oracle oinstall 286787 Aug 4 03:39 emrep_config.log

Where to search for pending alerts..is there any view?

Hi all,
I am using oracle 10g (10.2.0.4) on RHEL 4 update 7.
I have one question related to DB console, I have configured EM alerts for "Archive alert hung alert log error" metric. I configured my SMTP on DEC, but today I am getting alerts of dated 10th of NOV like below:
EM Alert: Clear: cmfn - Closing stateless severity.
Dont understand why its giving too late reply for this alert as "CLEAR".
Ideally when I configured my SMTP in DEC then at the same time it should sent all these pending/queued "critical/warning/clear" alerts.
I have checked through DBA_ALERT_HISTORY and DBA_OUTSTANDING_ALERTS but didnt seems any pending alert of NOV month.
Can any one suggest me?

Hi Guys,
Thanks for your suggestion, finally I got the solution for how to clear the pending alerts so there is no more pending dates emails in your mailbox.
I search it and find it out that those pending data comes from three tables: MGMT_CURRENT_SEVERITY, MGMT_SEVERITY_ANNOTATION, and MGMT_NOTIFICATION_LOG. The easiest way to delete from the driving table is to use a GUI tool such as SQL Manager or Toad. Delete the row, commit the transaction, refresh OEM, and the message will be gone.
This perfectly works for me. But one new problem arise that I dont see any operating system related error on OEM first page, as I had already a mail which stating that "/" partiton is having only 2G space remainig but when I checked with OEM ("RElated Alerts") there was not any alerts. what could be the reason?
Can any one havign any idea?
Thanks...

Tablespace threshold alerts?

Maybe 2 silly questions...
Say if I have a tablespace 80% full and then I set the warning threshold down to 75%, will the alert be generated immediately or delayed (how much?)
If I don't get warning even after 1 day ( with restart database ), what was wrong?

Hi,
I have checked the dba_threshold view the threshold has been set correctly as I saw in EM. (warning: 75, critical: 85, while my tablespace is now 77% full )
and there are no rows for dba_outstanding_alerts.
I remember there was an exam question like this as well but I don't know the correct answer.

Tablespace threshold alert

Hi,
I executed the below procedure to implement the tablespace threshold for the tablespace 'TESTING'.
My doubt is, once the threshold reaches where will I get the message like the tablespace 'TESTING' has only 51200 KB left.
Database:10.2.0.4
OS: solaris 10
BEGIN
DBMS_SERVER_ALERT.SET_THRESHOLD(
metrics_id => DBMS_SERVER_ALERT.TABLESPACE_BYT_FREE,
warning_operator => DBMS_SERVER_ALERT.OPERATOR_LE,
warning_value => '51200',
critical_operator => DBMS_SERVER_ALERT.OPERATOR_LE,
critical_value => '40960',
observation_period => 1,
consecutive_occurrences => 1,
instance_name => NULL,
object_type => DBMS_SERVER_ALERT.OBJECT_TYPE_TABLESPACE,
object_name => 'TESTING');
DBMS_SERVER_ALERT.SET_THRESHOLD(
metrics_id => DBMS_SERVER_ALERT.TABLESPACE_PCT_FULL,
warning_operator => DBMS_SERVER_ALERT.OPERATOR_GT,
warning_value => '0',
critical_operator => DBMS_SERVER_ALERT.OPERATOR_GT,
critical_value => '0',
observation_period => 1,
consecutive_occurrences => 1,
instance_name => NULL,
object_type => DBMS_SERVER_ALERT.OBJECT_TYPE_TABLESPACE,
object_name => 'TESTING');
END;
/

Just curious, why are you setting the second threshold (TABLESPACE_PCT_FULL) limit = 0 %?
Anyway, the view dba_outstanding_alerts does not reflect the status immediately. It may take a few minutes, even if the parameter observation_period = 1 (minute).
-- Here we have set the database to trigger an alert if the any tablespace usage exceeds 85%
SQL> select metrics_name, warning_operator, warning_value
2 from dba_thresholds
3 /
METRICS_NAME               WARNING_OPERATOR WARNING_VALUE
Tablespace Space Usage     GE               85
SQL> CREATE TABLESPACE "TS_TEST" LOGGING DATAFILE
2 'C:\ORADB\TRAIN10G\DATA\TS_TEST01.DBF' SIZE 400K AUTOEXTEND ON NEXT 100K MAXSIZE 800K
3 EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ;
Tablespace created
SQL> CREATE TABLE testtab (testcol CHAR(100)) tablespace TS_TEST;
Table created.
-- Here we wrote a script to insert 1000 rows at a time which will be run repeatedly until we see the threshold exceeded
DECLARE
N INTEGER;
BEGIN
   FOR N IN 1..1000 LOOP
      INSERT INTO testtab values('TESTTESTTEST');
   END LOOP;
   COMMIT;
END;
... repeated a few times, checking the freespace each round with the query below until the threshold is exceeded
SQL> SELECT a.tablespace_name
2         ,trunc(decode(a.autoextensible,'YES',a.maxsize-a.bytes+NVL(b.free,0),'NO',NVL(b.free,0))/1024) free_kb
3         ,trunc(a.bytes/1024) size_kb
4         ,trunc(a.maxsize/1024) maxsize_kb
5         ,a.autoextensible ae
6         ,trunc(decode(a.autoextensible,'YES',(a.maxsize-a.bytes+NVL(b.free,0))/a.maxsize*100,'NO',NVL(b.free,0)/a.maxsize*100)) free_pct
7    FROM ( select tablespace_name
8          ,autoextensible,sum(bytes) bytes
9          ,sum (decode(autoextensible,'YES',maxbytes,bytes)) maxsize
10           from dba_data_files
11           group by tablespace_name,autoextensible) a,
12          (select tablespace_name ,sum(bytes) free
13           from dba_free_space
14           group by tablespace_name) b
15 where a.tablespace_name=b.tablespace_name(+)
16 order by 2 asc
17 /
TABLESPACE_N    FREE_KB    SIZE_KB MAXSIZE_KB AE    FREE_PCT
TS_TEST              16        784        800 YES          2
... SQL below was repeatedly run, and after 4 minutes we got the alert in dba_outstanding_alerts....
SQL> select object_name, object_type, reason
2 from dba_outstanding_alerts
3 /
OBJECT_NAME     OBJECT_TYPE      REASON
TS_TEST         TABLESPACE       Tablespace [TS_TEST] is [88 percent] fullAlso, you can expand this method to include a stored procedure that is scheduled (DBMS_SCHEDULER) to check dba_outstanding_alerts every so often and compose an email message to be sent to the DBA using UTL_SMTP.

Database Time Spent Waiting (%)

In My RAC 11.2.0.2.2, I have the following warnings in the dba_outstanding_alerts,
How to clean them? I don't have Diagnostic Pack licensed for this environment; it's a test environment; I just have a basic license
REASON
METRIC_VALUE MESSAGE_TYPE TO_CHAR(CREATION_TIME,'DD-MON
HOST_ID
Metrics "Database Time Spent Waiting (%)" is at 34.11247 for event class "Concurrency"
34.1124716 Warning 15-JUL-2011 17:49:32
db03
Metrics "Database Time Spent Waiting (%)" is at 76.9712 for event class "Other"
76.9712048 Warning 15-JUL-2011 17:53:00
db02

Please read How To Clear An Alert http://blogs.oracle.com/oem/entry/how_to_clear_an_alert.

Help on failing RMAN backup please.

I have setup a nightly backup with the following script.
run {
allocate channel oem_backup_disk1 type disk format 'd:\mad3_nightly_backups\%U';
backup incremental level 1 cumulative as BACKUPSET tag 'MAD3_CUMULATIVE_BA_040506080003' database include current controlfile;
recover copy of database;
backup as BACKUPSET tag 'MAD3_CUMULATIVE_BA_040506080003' archivelog all not backed up delete all input;
report obsolete;
crosscheck backup;
crosscheck copy;
report need backup;
report unrecoverable;
release channel oem_backup_disk1;
But everytime I try to run this via OEM's nightly backup shedule, I get the error in the log below. But not able to identify what is causing the problem.
My database is currently about 300GB.
DB_RECOVERY_FILE_DEST_SIZE = 2GB
FLASHBACK_ON = NO
Shoud I try and increase the DB_RECOVERY_FILE_DEST_SIZE? If so to what? I would appriciate any help guys. Thanks.
channel oem_backup_disk1: starting incremental level 1 datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
input datafile fno=00005 name=+MAD3ASM/mad3/datafile/madattrib.277.586366645
.......SNIPED
input datafile fno=00025 name=+MAD3ASM/mad3/datafile/mmdatalive.419.586257801
input datafile fno=00027 name=+MAD3ASM/mad3/datafile/mmattrindexlive.421.586258381
input datafile fno=00028 name=+MAD3ASM/mad3/datafile/mmattrindexlive.422.586258471
input datafile fno=00026 name=+MAD3ASM/mad3/datafile/mmspindexlive.420.586258363
input datafile fno=00029 name=+MAD3ASM/mad3/datafile/mmdataarchive.423.586258563
input datafile fno=00030 name=+MAD3ASM/mad3/datafile/mmspindexarchive.424.586258581
input datafile fno=00031 name=+MAD3ASM/mad3/datafile/mmattrindexarchive.425.586258599
input datafile fno=00001 name=+MAD3ASM/mad3/datafile/system.256.583260945
input datafile fno=00003 name=+MAD3ASM/mad3/datafile/sysaux.257.583260945
input datafile fno=00002 name=+MAD3ASM/mad3/datafile/undotbs1.258.583260945
input datafile fno=00004 name=+MAD3ASM/mad3/datafile/users.259.583260947
channel oem_backup_disk1: starting piece 1 at 05-APR-06
channel oem_backup_disk1: finished piece 1 at 05-APR-06
piece handle=D:\MAD3_NIGHTLY_BACKUPS\3SHFPDMM_1_1 tag=MAD3_CUMULATIVE_BA_040506080003 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 01:33:55
channel oem_backup_disk1: starting incremental level 1 datafile backupset
channel oem_backup_disk1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel oem_backup_disk1: starting piece 1 at 05-APR-06
channel oem_backup_disk1: finished piece 1 at 05-APR-06
piece handle=D:\MAD3_NIGHTLY_BACKUPS\3THFPJ6P_1_1 tag=MAD3_CUMULATIVE_BA_040506080003 comment=NONE
channel oem_backup_disk1: backup set complete, elapsed time: 00:00:04
Finished backup at 05-APR-06
Starting recover at 05-APR-06
no copy of datafile 6 found to recover
no copy of datafile 7 found to recover
....SNIPED (from 8 to 29)
no copy of datafile 30 found to recover
no copy of datafile 31 found to recover
channel oem_backup_disk1: starting incremental datafile backupset restore
channel oem_backup_disk1: specifying datafile copies to recover
recovering datafile copy fno=00001 name=+MAD3ASM/mad3/datafile/system.392.586209619
recovering datafile copy fno=00002 name=+MAD3ASM/mad3/datafile/undotbs1.395.586209667
recovering datafile copy fno=00003 name=+MAD3ASM/mad3/datafile/sysaux.391.586209645
recovering datafile copy fno=00004 name=+MAD3ASM/mad3/datafile/users.396.586209669
recovering datafile copy fno=00005 name=+MAD3ASM/mad3/datafile/madattrib.768.586383235
channel oem_backup_disk1: reading from backup piece D:\MAD3_NIGHTLY_BACKUPS\3SHFPDMM_1_1
released channel: oem_backup_disk1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 04/05/2006 21:34:30
ORA-19870: error reading backup piece D:\MAD3_NIGHTLY_BACKUPS\3SHFPDMM_1_1
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 13904117760 bytes disk space from 2147483648 limit
exit;
Recovery Manager complete.

Take a look at this metalink note: 305812.1
Flash Recovery area - Space management Warning & Alerts: https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=305812.1
SELECT object_type, message_type, message_level, reason, suggested_action
FROM dba_outstanding_alerts;
The following actions can be done to resolve the space issue :
- Add disk space to the Flash Recovery Area.
- Back up your files to a tertiary device.
- Delete the files from the Flash Recovery Area using RMAN.
- Changing RMAN retention policy.
Bye, Aron

MMON Deadlock

Hi All,
Strange situation today at the office.
My system:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
PL/SQL Release 11.1.0.6.0 - Production
"CORE 11.1.0.6.0 Production"
TNS for IBM/AIX RISC System/6000: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - Production
select * from dba_outstanding_alerts;
Metrics "Database Time Spent Waiting (%)" is at 100 for event class "Concurrency"
Metrics "Database Time Spent Waiting (%)" is at 100 for event class "Other"
Session 551 is blocking 2 other sessions
Session 501 is blocking 2 other sessions
Session 501 is from program M001 so seems to be MMON
MMON => Managebility Monitor is the enabling process for many of the self-monitoring and self-tuning capabilities,
MMON captures statistics which are used by ADDM.
Having select * from dba_advisor_tasks it seems i am missing snapshots for the last 3 days.
My assumption is that this situation is a deadlock of MMON,
i resolved the issue by startup force, but when we have moved to production I don't want to be doing startup force.
How would I resolve this issue since I am not able to kill system sessions, and without resolving this deadlock some processes can't be run,
but I don't want to do startup force.....
Any reflections on this?
Thanks!

From my private test system I killed the MMON process and it restarted,
so it seems an option to kill the MMON process using kill -9.
But I am unsure if this is the preferred option.
Any reflections.

Capacity planning of database objects

Oracle 10.2.0.4
Windows platform
I was reading Oracle Admin Guide :- Capacity planning of database objects section, but these and most of other sections are very theoretical .
Kindly suggest how to get these topics in better way.

I think Reddy has it right: watch the trend in space usage primarily at the tablespace level but you would also want to take a look at the individual tables and indexes within a tablespace to spot the fast growers, to pick out tables that might need parameter adjustment (pct_free) to avoid row migration, to identify indexes that may not reach a reasonable stready state size, etc....
The dba_outstanding_alerts and related views might be of interest.
On occassion just taking a count(*) of how many application tables, indexes, and users exist on your system and storing this with space usage figures can also be useful information when it comes time to request more disk, cpu, or memory since you can show past growth.
HTH -- Mark D Powell --

Alert history

Hi all,I have one question. I know that, when i want monitoring database alert then i can use following views:
DBA_THRESHOLDS, DBA_OUTSTANDING_ALERTS,DBA_ALERT_HISTORY,dba_hist_xxx
at this views the minimum date is '28-jul-09'
But i monitor database with enterprise manager i see also past date such as '16-may-09';
I want know that, which others views enterprise manager use ?

Depending on version, edition and if you've purchased the licenses (see [Licensing guide|http://download.oracle.com/docs/cd/B19306_01/license.102/b14199/options.htm] about management packs), you could refer to the DBA_HIST views. OEM Database Control (and Grid Control) have additional tables and views, likely also additionally licensed, part of the SYSMAN schema.

Dba_outstanding_alerts

Similar Messages

Maybe you are looking for