Re: Trace file getting huge
From: Rich Jesse <rjoralist3_at_society.servebeer.com>
Date: Wed, 5 Feb 2014 11:50:08 -0600 (CST)
Message-ID: <74790103a86ffd14065a7ff3e7385ade.squirrel_at_society.servebeer.com>
Saad writes:
Date: Wed, 5 Feb 2014 11:50:08 -0600 (CST)
Message-ID: <74790103a86ffd14065a7ff3e7385ade.squirrel_at_society.servebeer.com>
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-lReceived on Wed Feb 05 2014 - 18:50:08 CET