RE: Archiving events (#20 error) sent to W2K event viewer - application log

  • From: "Igor Neyman" <ineyman@xxxxxxxxxxxxxx>
  • To: <bdbafh@xxxxxxxxx>, <qnxodba@xxxxxxxxx>
  • Date: Fri, 14 Jan 2005 16:42:13 -0500

There was a discussion on this list couple weeks ago regarding this

There is a hidden parameter "_disable_ntlog_events", which supposed (if
set to FALSE) to stop oracle from writing this info into Event Log.
Unfortunatily on it didn't work for me - oracle bug.
As Niall mentioned, it's supposed to be fixed in

Igor Neyman, OCP DBA

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Paul Drake
Sent: Friday, January 14, 2005 3:43 PM
To: qnxodba@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Archiving events (#20 error) sent to W2K event viewer -
application log


Did anyone ever reply on this issue?
Did you find out what the cause was?

I'm tempted to open an iTAR on this issue as a quick search found
nothing in particular.
No way do I want to have to deal with this error for every logfile
switch on production servers with on win32 (w2k adv svr sp4,



On Tue, 19 Oct 2004 15:39:07 -0400, mhthomas <qnxodba@xxxxxxxxx> wrote:
> Hi,
> 1) Does anyone know how to stop event #20 errors going into W2K event
> viewer - application log? (assuming I'm not actually making the
> error).
> Ref: Metalink note - 67868.1
> 20 - Error, Archive Process Error
> 2) I'm upgrading 10g from to and noticing /too many/
> events in application log. I reconfigured my application log to roll
> over (default setting: flush in 7 days may fill w/error). But, I don't
> like to see a bunch of 'errors' based on archiving tasks.
> Example text: "The description for Event ID (20) in Source
> (Oracle.<mysid>) cannot be found. ...bunch of junk... event: ARC1:
> Closing local archive destination LOG_ARCHIVE_DEST_1: '<my archive
> path>\archive\arc00136_-538785985.001' (<mysid>)
> Each archive log action creates /four/ items in Application Log.
> Begin, Create, Complete, Close archiving (close example above)
> 3) I do not have any errors in my alert log, and archiving messages
> appear normal in the alert log. Therefore, I believe my archiving
> coniguration is a-okay.
> Regards,
> Mike Thomas
> --
> //


Other related posts: