We have five databases running on an AIX 5.3 server. Let's call it our primary server.
The server is booted every week (don't ask why...).
The users have complained off and on about the database not being available when they expect it to be. They receive an ora-3113.
In looking at the alert.log of the instances, it shows that the instances shutdown normally upon server shutdown and then restart automatically after server restart. However, then it seems that the database instances (all five of them) shutdown (abort) and then restart again.
This server is a primary server in a dataguard environment for four of the databases. This problem occurs for all five so I don't think it's related to dataguard. The standby database is running four instances and although it is set up exactly as the primary, it does not encounter this issue after a server boot.
In the past, the only time I've seen the alert.log show a 'shutdown (abort)' like that is if the 'dbstart' is issued against an already running instance.
We have an entry in the /etc/oratab to start the listener and then execute the 'dbstart' script.
Is it possible that there is a setting somewhere that is re-issuing the 'dbstart' script? We can't figure it out. It seems this has been going on for some time now and we are only now realizing it because the user's complained.
Have compared /etc/inittabs and 'dbstart' scripts in both servers and they are identical.
Of course, we are assuming that I'm reading the alert log correctly. I will upload a snippet of our alert log during the boot process. ALERT-FOR-EE.log