Re: Trace file getting huge

From: Saad Khan <saad4u_at_gmail.com>
Date: Wed, 5 Feb 2014 13:32:51 -0500
Message-ID: <CACqGOPKr1NC_+z6LiEkZ5gFLFw9PozAN=cYrLOpS=AzqkBUw9w_at_mail.gmail.com>



Thanks Rich. I wish it could be that simple. But no jobs scheduled.

Oracle has come up with response to take a look at doc 1449015.1 which is regarding an unpublished bug 13073122 which is fixed in 12.1

will keep you posted.

On Wed, Feb 5, 2014 at 12:50 PM, Rich Jesse < rjoralist3_at_society.servebeer.com> wrote:

> Saad writes:
>
> > Fellows,
> > Oracle came up with the famous solution of "Reboot the server". Before
> > rebooting I noticed that when I shoutdown both databases and oracle
> > services, the megasized trace file (<.._j0002_..trc) was gone. Server
> was
> > rebooted but as soon as Oracle services started, it started dumping trace
> > again and the similar j0002.trc file hit 4GB size within 2 min.
> >
> > Alert file is full of these messages:
> > Errors in file e:\ora11g\diag\rdbms\qmdb\qmdb\trace\qmdb_j002_3288.trc:
>
> Have you looked at DBA_SCHEDULER_RUNNING_JOBS to see what that job might
> be?
> Perhaps the job is setting its own events...
>
> GL!
>
> Rich
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Feb 05 2014 - 19:32:51 CET

Original text of this message