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 -- //www.freelists.org/webpage/oracle-l