Thanks Pedro. Was able to find the error in /var/svc/log/milestone-multi-user:default.log. Now to figure out why dbhome is not found during reboot. Perhaps because dbhome is not found in /usr/bin. Will begin investigation. Executing legacy init script "/etc/rc2.d/S99oracle". Oracle Startup/Shutdown Begins /etc/rc2.d/S99oracle: dbhome: not found ORACLE_HOME = [] ? /etc/rc2.d/S99oracle: test: argument expected Legacy init script "/etc/rc2.d/S99oracle" exited with return code 1. On Jan 9, 2008 1:32 PM, Pedro Espinoza <raindoctor@xxxxxxxxx> wrote: > Given it is solaris 10, the whole rc scripts are legacy services, > which in turn are controlled by svc.startd. Definitely, there should > be logs in /var/svc/log/*. > > You should get something like the following: > > milestone-multi-user-server:default.log:Executing legacy init script > "/etc/rc3.d/S911oracle". > milestone-multi-user-server:default.log:Legacy init script > "/etc/rc3.d/S911oracle" exited with return code 0. > > > On Jan 8, 2008 10:17 PM, Mike Rothouse <mrothouse@xxxxxxxxx> wrote: > > Oracle 10.2.0.3 on Solaris 10 (64-bit SPARC) > > > > I'm having a problem getting my Oracle database to auto-start upon > reboot > > (init -6) on . Yet when I run the dbora script manually (./dbora start) > > using the root account, the database starts without a problem ( i.e. the > > script works as expected). > > > > -rwxr-xr-x 1 oracle dba 1193 Nov 18 19:03 /etc/init.d/dbora > > > > lrwxrwxrwx 1 root root 17 Jan 7 11:20 /etc/rc0.d/K01oracle > -> > > /etc/init.d/dbora > > > > lrwxrwxrwx 1 root root 17 Jan 7 11:19 /etc/rc2.d/S99oracle > -> > > /etc/init.d/dbora > > > > My UNIX Admin tells me there are no errors in any log files during the > > reboot. I wouldn't expect any errors as it seems to skip both shutdown > and > > startup of Oracle and as previously mentioned I am successful (shutdown > and > > startup) when running the script manually after the server is up. > > > > I don't encounter this problem on another server running Solaris > 9/Oracle > > 10.2.0.3, so I'm not sure if Solaris 10 is somehow different. > > > > Anyone else encounter this problem on Solaris 10 and find a resolution? >