Re: How to test if OEM12c (12.1.0.5) detect and alert archiver hung without actually create a archive hung - production database

Do you not have a suitable dev/test environment? As Matt says you can write whatever you want to the alert.log, but you really ought to treat you alerting to the same dev/test cycle as your applications and patching I would have thought.

On Tue, Jul 19, 2016 at 4:37 PM, Le, Binh T. <Binh.Le_at_lfg.com> wrote:

> Dear List,
>
>
>
> I setup the oracle database instance target with metric DB Alert Log >
> Archiver Hung Alert Log Error with Critical Threshold as ORA-.
>
>
>
> As Oracle document says that it “should” alert when log.xml under alert
> directory content the error.
>
>
>
> Is there the way to inject the error so that OEM will detect and send out
> the alert.
>
>
>
> It is production database so I can’t not actually cause archive hung
> without getting fired.
>
>
>
> I copied the error from other database log over but doesn’t seem alert.
>
>
>
> Thanks,
>
> Binh
>
> Notice of Confidentiality: **This E-mail and any of its attachments may
> contain
> Lincoln National Corporation proprietary information, which is privileged,
> confidential,
> or subject to copyright belonging to the Lincoln National Corporation
> family of
> companies. This E-mail is intended solely for the use of the individual or
> entity to
> which it is addressed. If you are not the intended recipient of this
> E-mail, you are
> hereby notified that any dissemination, distribution, copying, or action
> taken in
> relation to the contents of and attachments to this E-mail is strictly
> prohibited
> and may be unlawful. If you have received this E-mail in error, please
> notify the
> sender immediately and permanently delete the original and any copy of
> this E-mail
> and any printout. Thank You.**
>

-- 
Niall Litchfield
Oracle DBA
http://www.orawin.info

--
http://www.freelists.org/webpage/oracle-l