SQL Session Trace files generating out of control - How do I stop???
668490Nov 5 2009 — edited Nov 5 2009I have a production 11.1.0.7 database running and somehow it is generating trace files to the diag trace directory at a rate of 4 per minute filling up the filesystem.
No sql_trace or 10046 are set at database level. I suspect possibly that some performace monitoring feature in OEM Grid Control was set but we cannot figure out how to turn it off within Grid Control.
I cannot imagine there is not a way to turn this tracing off unless a developer has imbedded the command to turn session tracing on within the application external to the database.
Orace Metalink cannot figure it out either.
If I simply bounce the database will this kill the tracing of course unless it is in the code of the application somewhere but at least I could test by logging in and running some SQL without the application being connected and seeing if the tracing still continues.
Has this happen to anyone out there? Any suggestions would be very welcome.