oracle listener startup issue for the OPEDS virtual zones (Oracle Solaris Zones)
OCCASIONALLY, upon morning startup at 0520 local server time, the oracle listener fails to start up on one or more of the migrated zones.. This causes a myriad of problems with all OPEDS applications that access the oracle database, and renders the district represented by that zone unusable; that standard SEV 1 outage. The reason that the listener will not start is because there is a file (or file descriptor) in the /var/tmp/.oracle directory that is being held open by some process. That file must be removed which allows the listener to start. The files, and entire directory for that matter, are owned by oracle:dba. However oracle cannot remove that file. We must call in an SA( System Eng) to remove the /var/tmp/.oracle directory from the server