Oracle 11g Init Script

readme.md

Oracle 11g Init Script

Add to OEL:

chkconfig --add dbora 

dbora

#!/bin/sh  -x
#
# dbora: Starts the oracle database
#
# chkconfig: 345 99 01
# description: Starts or stops oracle db
# config:

# Change the value of ORACLE_HOME to specify the correct Oracle home
# directory for you installation

ORACLE_HOME=/home/oracle/app/oracle/product/11.2.0/dbhome_1
#
# change the value of ORACLE to the login name of the 
# oracle owner at your site
#

ORACLE=oracle

PATH=${PATH}:$ORACLE_HOME/bin
HOST=`hostname`
PLATFORM=`uname`
export ORACLE_HOME PATH
LOG=$ORACLE_HOME/startup.log
touch $LOG
chown $ORACLE:dba $LOG
chmod a+r $LOG
#

case $1 in
'start')
        echo "$0: starting up" >> $LOG
        date >> $LOG
        # Start Oracle Net
        if [ -f $ORACLE_HOME/bin/tnslsnr ] ; then
             echo "starting Oracle Net Listener"
             su - $ORACLE -c "$ORACLE_HOME/bin/lsnrctl start >> $LOG 2>&1 &"
        fi
        echo "Starting Oracle databases"
        su - $ORACLE -c "$ORACLE_HOME/bin/dbstart >> $LOG 2>&1 &"
        ;;
'stop')
        echo "$0: shutting down" >> $LOG
        date >> $LOG
        # Stop Oracle Net
        if [ -f $ORACLE_HOME/bin/tnslsnr ] ; then
             echo "stopping Oracle Net Listener"
             su - $ORACLE -c "$ORACLE_HOME/bin/lsnrctl stop >> $LOG 2>&1 &"
        fi
        echo "stopping Oracle databases"
        su - $ORACLE -c "$ORACLE_HOME/bin/dbshut >> $LOG 2>&1 &"
        ;;
*)
        echo "usage: $0 {start|stop}" 
        exit 
        ;;
esac
#
exit

provision.sh

#!/bin/bash

# Usage: sudo bash /vagrant/scripts/provision.sh

# Provisions the required tablespaces and schema required 
# for a working FMC3 database
su - oracle << SUEOF
echo "Waiting for oracle to start... "
LOG=\$ORACLE_HOME/startup.log
tail -n 5 -f \$LOG | grep -m 1 "Database instance \"ORCL\" warm started." | xargs echo "" >> \$LOG \;
echo "... detected that oracle has started"

sqlplus /nolog <<EOF
connect /as sysdba

SPOOL vagrant-init.log

alter system set sec_case_sensitive_logon=false scope=both;

SET ECHO ON

@/vagrant/scripts/create-tablespaces.sql

@/vagrant/scripts/create-schemas.sql

@/vagrant/scripts/create-fmc3ro.sql

exit;
EOF

SUEOF

exit 0;

Vagrantfile

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  # All Vagrant configuration is done here. The most common configuration
  # options are documented and commented below. For a complete reference,
  # please see the online documentation at vagrantup.com.

  # Every Vagrant virtual environment requires a box to build off of.
  config.vm.box = "ORCL_11gR211203_v1"

  # The url from where the 'config.vm.box' box will be fetched if it
  # doesn't already exist on the user's system.
  config.vm.box_url = "http://code.geomatic.com.au/vagrant/boxes/ORCL_11gR211203_v1.0.0.box"

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  config.vm.network :forwarded_port, guest: 1521, host: 21521
  
  config.vm.provision :shell, :inline => "sudo bash /vagrant/scripts/provision.sh > provision.log"

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network :private_network, ip: "192.168.33.10"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network :public_network

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider :virtualbox do |vb|
  #   # Don't boot with headless mode
  #   vb.gui = true
  #
  #   # Use VBoxManage to customize the VM. For example to change memory:
  #   vb.customize ["modifyvm", :id, "--memory", "1024"]
  # end
  #
  # View the documentation for the provider you're using for more
  # information on available options.

  # Enable provisioning with Puppet stand alone.  Puppet manifests
  # are contained in a directory path relative to this Vagrantfile.
  # You will need to create the manifests directory and a manifest in
  # the file precise32.pp in the manifests_path directory.
  #
  # An example Puppet manifest to provision the message of the day:
  #
  # # group { "puppet":
  # #   ensure => "present",
  # # }
  # #
  # # File { owner => 0, group => 0, mode => 0644 }
  # #
  # # file { '/etc/motd':
  # #   content => "Welcome to your Vagrant-built virtual machine!
  # #               Managed by Puppet.\n"
  # # }
  #
  # config.vm.provision :puppet do |puppet|
  #   puppet.manifests_path = "manifests"
  #   puppet.manifest_file  = "precise32.pp"
  # end

  # Enable provisioning with chef solo, specifying a cookbooks path, roles
  # path, and data_bags path (all relative to this Vagrantfile), and adding
  # some recipes and/or roles.
  #
  # config.vm.provision :chef_solo do |chef|
  #   chef.cookbooks_path = "../my-recipes/cookbooks"
  #   chef.roles_path = "../my-recipes/roles"
  #   chef.data_bags_path = "../my-recipes/data_bags"
  #   chef.add_recipe "mysql"
  #   chef.add_role "web"
  #
  #   # You may also specify custom JSON attributes:
  #   chef.json = { :mysql_password => "foo" }
  # end

  # Enable provisioning with chef server, specifying the chef server URL,
  # and the path to the validation key (relative to this Vagrantfile).
  #
  # The Opscode Platform uses HTTPS. Substitute your organization for
  # ORGNAME in the URL and validation key.
  #
  # If you have your own Chef Server, use the appropriate URL, which may be
  # HTTP instead of HTTPS depending on your configuration. Also change the
  # validation key to validation.pem.
  #
  # config.vm.provision :chef_client do |chef|
  #   chef.chef_server_url = "https://api.opscode.com/organizations/ORGNAME"
  #   chef.validation_key_path = "ORGNAME-validator.pem"
  # end
  #
  # If you're using the Opscode platform, your validator client is
  # ORGNAME-validator, replacing ORGNAME with your organization name.
  #
  # If you have your own Chef Server, the default validation client name is
  # chef-validator, unless you changed the configuration.
  #
  #   chef.validation_client_name = "ORGNAME-validator"
end