2 Stopping and Starting Oracle Software

2.1.1 Stopping and Starting Oracle Database and Oracle Automatic Storage Management Instances

This section describes how to stop and start Oracle Database and Oracle Automatic Storage Management instances.

2.1.2 Stopping and Starting Oracle Restart

To stop or start Oracle Restart, run the following command:

• Start: This option is used to start Oracle Restart

  Syntax and Options:

  crsctl start has
  

• Stop: This option is used to stop Oracle Restart

  Syntax and Options:

  crsctl stop has
  

  See Also:

  Oracle Database Administrator's Guide for more information about the srvctl commands

2.2.1 Automating Database Startup and Shutdown on Other Operating Systems

To automate database startup and shutdown by using the dbstart and dbshut scripts:

1. Log in as the root user.

2. Edit the oratab file for the platform.

   To open the file, use one of the following commands:

   • On Oracle Solaris:

     # vi /var/opt/oracle/oratab
     

   • On IBM AIX on POWER Systems (64-Bit) and Linux:

     # vi /etc/oratab
     

   Database entries in the oratab file are displayed in the following format:

   $ORACLE_SID:$ORACLE_HOME:<N|Y>
   

   In this example, the values Y and N specify whether you want the scripts to start or shut down the database, respectively. For each database for which you want to automate shutdown and startup, first determine the instance identifier (SID) for that database, which is identified by the SID in the first field. Then, change the last field for each to Y.

   You can set dbstart to autostart a single-instance database which uses an Automatic Storage Management installation auto-started by Oracle Clusterware. This is the default behavior for an Automatic Storage Management cluster. To do this, you must change the oratab entry of the database and the Automatic Storage Management installation to use a third field with the value W and N, respectively. These values specify that dbstart auto-starts the database only after the Automatic Storage Management instance is started.

   Note:

   If you add new database instances to the system and automate the startup for them, then you must edit the entries for those instances in the oratab file.

3. Change directory to one of the following, depending on the operating system:

   Platform	Initialization File Directory
   Linux and Oracle Solaris	/etc/init.d
   IBM AIX on POWER Systems (64-Bit)	/etc

   
   

4. Create a file called dbora, and copy the following lines into this file:

   Note:

   Change the value of the ORACLE_HOME environment variable to specify the Oracle home directory for the installation. Change the value of the ORACLE environment variable to the user name of the owner of the database installed in the Oracle home directory (typically, oracle).

   #! /bin/sh 
   #
   # Change the value of ORACLE_HOME to specify the correct Oracle home
   # directory for your installation.
   
   ORACLE_HOME=/u01/app/oracle/product/12.1.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
   #
   if [ ! "$2" = "ORA_DB" ] ; then
         runuser -l $ORACLE  $0 $1 ORA_DB
         if [ "$PLATFORM" = "Linux" ] ; then
            touch /var/lock/subsys/dbora
         fi
         exit
      fi
   #
   case $1 in
   'start')
           $ORACLE_HOME/bin/dbstart $ORACLE_HOME &
           ;;
   'stop')
           $ORACLE_HOME/bin/dbshut $ORACLE_HOME &
           rm -f /var/lock/subsys/dbora
           ;;
   *)
           echo "usage: $0 {start|stop}"
           exit
           ;;
   esac
   #
   exit
   

   Note:

   This script can only stop Oracle Net listener for which a password has not been set. In addition, if the listener name is not the default name, LISTENER, then you must specify the listener name in the stop and start commands:

   $ORACLE_HOME/bin/lsnrctl {start|stop} listener_name
   

5. Change the group of the dbora file to the OSDBA group (typically dba), and set the permissions to 750:

   # chgrp dba dbora
   # chmod 750 dbora
   

6. Create symbolic links to the dbora script in the appropriate run-level script directories, as follows:

   Platform	Symbolic Links Commands
   Oracle Solaris	# ln -s /etc/init.d/dbora /etc/rc0.d/K01dbora # ln -s /etc/init.d/dbora /etc/rc3.d/S99dbora
   Linux	# ln -s /etc/init.d/dbora /etc/rc.d/rc0.d/K01dbora # ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/S99dbora # ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/S99dbora
   IBM AIX on POWER Systems (64-Bit)	# ln -s /etc/dbora /etc/rc.d/rc2.d/S99dbora # ln -s /etc/dbora /etc/rc.d/rc0.d/K01dbora