More issues with alert.log
I am cross-posting this to oracle-l as well.
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.
0