Re: Oracle 11g placement of the alert log
Date: 12 Jan 2008 16:08:19 GMT
Message-ID: <4788e5f3$0$1342$834e42db@reader.greatnowhere.com>
On Sat, 12 Jan 2008 15:47:02 +0000, Mladen Gogala wrote:
> This is untrue. One can simply change background_dump_dest and the alert
> log will go back to where it was.
>
Those parametes are, of course, deprecated in favor of DIAGNOSTIC_DEST but are still fully functional. Nobody will lose support for doing that. Scripts should, of course, be changed, but if that is for some reason inconvenient, one can reset the traditional *_DUMP_DEST parameters and have it all back. I am haven't tried accessing v$diag_info after that, so I am not sure whether it will work. DIAG_DEST is also priceless because of log.xml in the DIAGNOSTIC_DEST/alert directory which contains a timestamp for EVERY MESSAGE! Now that is something:
<msg time='2007-08-28T11:22:48.796-04:00' org_id='oracle' comp_id='rdbms'
msg_id='opistr_real:871:3971575317' type='NOTIFICATION' group='startup'
level='16' pid='25330' version='1'>
<txt>Starting ORACLE instance (normal)
</txt>
</msg>
<msg time='2007-08-28T11:22:49.362-04:00' org_id='oracle' comp_id='rdbms'
msg_id='ksunfy:13399:2937430291' type='NOTIFICATION' group='startup'
level='16' pid='25330'>
<txt>LICENSE_MAX_SESSION = 0
</txt>
</msg>
<msg time='2007-08-28T11:22:49.363-04:00' org_id='oracle' comp_id='rdbms'
msg_id='ksunfy:13400:4207019197' type='NOTIFICATION' group='startup'
level='16' pid='25330'>
<txt>LICENSE_SESSIONS_WARNING = 0
</txt>
</msg>
<msg time='2007-08-28T11:22:49.450-04:00' org_id='oracle' comp_id='rdbms'
type='UNKNOWN' level='16' pid='25330'>
<txt>Shared memory segment for instance monitoring created
</txt>
</msg>
Now, it is possible to create a parser (using, of course, XML parsing modules from CPAN) and search for the interesting error messages by time.
-- http://mgogala.freehostia.comReceived on Sat Jan 12 2008 - 10:08:19 CST