RE: X$DBGALERTEXT

From: Wolfson Larry - lwolfs <lawrence.wolfson_at_acxiom.com>
Date: Thu, 5 Jan 2012 16:04:36 +0000
Message-ID: <EDA437CAA8612C418E013CDA4B4A75516339D065_at_CWYIGMBCRP01.Corp.Acxiom.net>



Thanks Andy, Niall.
Sorry If I wasn't clear. On the Skipped a lot I just didn't send every day. On the bottom you saw 102 rows selected.

  But I do remember about the 10MB rotation you mentioned.

I'll check the note and Controls.
From: andyklock_at_gmail.com [mailto:andyklock_at_gmail.com] On Behalf Of Andy Klock Sent: Thursday, January 05, 2012 9:09 AM To: niall.litchfield_at_gmail.com
Cc: Wolfson Larry - lwolfs; oracle-l_at_freelists.org Subject: Re: X$DBGALERTEXT

That's exactly what it is. If you remove those "log(_nn).xml" files with adrci purge or the old fashioned way (rm), querying X$DBGALERTEXT will only return rows for what is available. The XML version of the alert logs are automatically purged based on the LONG_POLICY (which is 365 days by default). The current purge policy settings for long and short term can be seen (and set) with adrci (show control, set control).

As for, "> Skipped a lot" , Oracle automatically rotates the alert logs when they reach 10MB. I've never found a way to set this to something other than 10MB. I've done some testing back in the day and noticed that I could create gaps in the log sequence and this does confuse ADRCI and X$DBGALERTEXT. If you look in the DIAG_DEST\<db_name>\<instance_name>\alert directory look to see that you don't have any gaps in the log sequence.

For determining what is short and what is long it is described here:

Which Files Are Part Of SHORTP_POLICY And LONGP_POLICY In ADR? [ID 975448.1]

Andy
On Thu, Jan 5, 2012 at 7:07 AM, Niall Litchfield <niall.litchfield_at_gmail.com<mailto:niall.litchfield_at_gmail.com>> wrote: Larry
An excellent question. The table appears to essentially be some sort of external table built on the log.xml file in the DIAG_DEST\<db_name>\<instance_name>\alert directory (i.e not on the trace file version). As such the contents *ought* to be controlled by the purge policies for the ADR_HOME and or any manual purging you have in place. However in my quick tests in 11.2.0.3 on windows this doesn't seem to be the case.

I'd be really grateful as well if there was a clear definitive reference for what is subject to the short purge policy and what to the long purge policy - incidents are defined in the docs but the other diag_dest contents don't seem to be there.

Niall



The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged.

If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.

Thank You.


--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jan 05 2012 - 10:04:36 CST

Original text of this message