Open steveswinsburg opened 7 years ago
Since the /vagrant folder is mounted after the server starts up, if this takes a while the Database may not startup. The workaround is to connect and open it:
sudo su - oracle sqlplus "/ as sysdba" SQL> select status from v$instance;
the result should be MOUNTED. If so:
SQL> alter database open;
To resolve this, the Oracle startup could wait for the folder to be mounted via: http://razius.com/articles/launching-services-after-vagrant-mount/
Since the /vagrant folder is mounted after the server starts up, if this takes a while the Database may not startup. The workaround is to connect and open it:
the result should be MOUNTED. If so:
To resolve this, the Oracle startup could wait for the folder to be mounted via: http://razius.com/articles/launching-services-after-vagrant-mount/