More issues with alert.log

Good day, Listers,

In light of the issue with $ORACLE_HOME/dbs/alert_$ORACLE_SID.log in 11g
databases, I am curious about processes that write/create this file. So far,
we have tracked it down to incoming LOCAL connections (using pfiles on
alert_$ORACLE_SID.log with opensnoop) . However I am at a loss why
an incoming connection would arbitrarily write
to $ORACLE_HOME/dbs/alert_$ORACLE_SID.log instead of the one defined
by diagnostic_dest.

How would I determine exactly what is going on? I am not looking for
guesses, but scientific ways to go about getting that information.

To make matters worse, this seems like a very intermittent issue and not
easily reproducible. We have seen the issue occur about once per day since
upgrading to 11.1.0.7.7 last week. We are also receiving frequent core
dumps, why may be completely irrelevant - so far, I have not been able to
reconcile a core dump to an alert-log-spawning connection.

-- 
Charles Schultz

Other related posts: