missing alert.log mystery (it's not what you think)
Environment: Oracle EE 11.1.0.7 on Solaris 10
I know, the first thing that comes to mind "Oh yeah, the binary_dump_destination is overridden by diag_destination in 11g". That's not the problem here.
The next thing you think "Well, it could be an orphaned inode (ie, deleting a file that is open by another process)". That is also not the problem.
We have an alert.log that was last updated by the database on May 6th. Strangely enough, the log.xml in the alert directory of the diag destination is being updated normally, it is just the plain text alert.log in the trace directory that is not updated. We have bounced the database, changed the diag_destination parameter and I have even grepped all the file descriptors in /proc/*/fd for traces of a possibly opened alert.log - nothing, the alert.log is still not being updated. I tried dbms_system.ksdwrt to force a write to the alert.log - again, the log.xml is updated, the plain text
I know, the first thing that comes to mind "Oh yeah, the binary_dump_destination is overridden by diag_destination in 11g". That's not the problem here.
The next thing you think "Well, it could be an orphaned inode (ie, deleting a file that is open by another process)". That is also not the problem.
We have an alert.log that was last updated by the database on May 6th. Strangely enough, the log.xml in the alert directory of the diag destination is being updated normally, it is just the plain text alert.log in the trace directory that is not updated. We have bounced the database, changed the diag_destination parameter and I have even grepped all the file descriptors in /proc/*/fd for traces of a possibly opened alert.log - nothing, the alert.log is still not being updated. I tried dbms_system.ksdwrt to force a write to the alert.log - again, the log.xml is updated, the plain text
0