Re: X$DBGALERTEXT
- From: Andy Klock <andy@xxxxxxxxxxxxxxx>
- To: niall.litchfield@xxxxxxxxx
- Date: Thu, 5 Jan 2012 10:08:34 -0500
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@xxxxxxxxx
> 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
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
