PRIMECLUSTER Wizard for Oracle 4.5 Configuration and Administration Guide

3.1.1 Oracle resources Startup and Shutdown

Oracle instance Startup

Startup procedure of an Oracle instance is as follows:

1. su - <Oracle user>

2. sqlplus /nolog

3. connect / as sysdba

4. startup nomount or startup mount

5. alter database mount; (if "startup nomount" was executed at step "4")

6. alter database open;

7. alter pluggable database all open (if UsePDB of Oracle instance resource is set to yes.)

   In the Oracle Data Guard/Oracle Active Data Guard environment, when the CDB started to the OPEN state, which is able to start the PDBs, this command is executed. For details, see "Starting and Stopping CDB and PDB" in "F.1 Feature Outline".

• Initialized parameter file and server parameter file

  The initialized parameter file is not specified for Oracle instance startup through PRIMECLUSTER Wizard for Oracle, so the default initialized parameter file will be used instead. Specify the initialized parameter file for the following default path (symbolic link).

  <$ORACLE_HOME>/dbs/init<$ORACLE_SID>.ora

  The server parameter file should be located in the shared disk because it is dynamically changed. When you use the server parameter file, specify the full path of the server parameter file to the initialization parameter file. Refer to "2.2.6 Oracle Database Creation and Setting".
  It is recommended that the initialization parameter file settings are the same on the operating nodes and standby nodes.

  Note

  In single-node cluster operation, the definition described at "Initialized parameter file and server parameter file" is not necessary.

• Recovery processing

  PRIMECLUSTER Wizard for Oracle recovers the Oracle instance in the following cases:

  • When there is ACTIVE table space in the V$BACKUP view.

  • When there are files required to be recovered in the V$RECOVER_FILE view.

• DBA authentication

  PRIMECLUSTER Wizard for Oracle connects to Oracle instance with SYSDBA system privilege to start up or stop Oracle instance/database. In this case, local connection in operating system authentication is used.

Oracle instance Shutdown

• Shutdown procedure of an Oracle instance by user operation is as follows:

  1. su - <Oracle user>

  2. sqlplus /nolog

  3. connect / as sysdba

  4. shutdown <immediate / abort / transactional> (Setup with StopModeStop)
     Default : immediate

  5. If Oracle instance is not stopped at step "4" (except for abort), use shutdown abort.

  6. If Oracle instance is not stopped at step "4" or "5", shut it down forcibly by sending SIGKILL to the background processes.

• Shutdown procedure of an Oracle instance by resource failure or failover is as follows:

  1. su - <Oracle user>

  2. sqlplus /nolog

  3. connect / as sysdba

  4. shutdown <immediate / abort> (Setup with StopModeFail)
     Default : abort

  5. If Oracle instance is not stopped at step "4" (except for abort), use shutdown abort.

  6. If Oracle instance is not stopped at step "4" or "5", shut it down forcibly by sending SIGKILL to the background processes.

Even if UsePDB of Oracle instance resource is set to yes, PDBs is not stopped. PDBs stops by stopping the CDB.

Listener Startup

Startup procedure of a Listener is as follows:

1. su - <Oracle user>

2. lsnrctl start <ListenerName>

3. Makes sure that a Listener process does exist.

Listener Shutdown

Shutdown procedure of a Listener is as follows:

1. su - <Oracle user>

2. lsnrctl stop <ListenerName>

3. Makes sure that a Listener process does not exist.

4. If Listener is not stopped at step "3", shut it down forcibly by sending SIGKILL to the background process.

Oracle ASM instance Startup

Startup procedure of an Oracle ASM instance is as follows:

• Oracle Database 11g R2/12c R1(12.1.0.1)

  1. su - <Oracle user>

  2. sqlplus /nolog

  3. connect / as sysasm

  4. startup mount; (if "STARTED" already, "alter diskgroup all mount" is executed.)

• Oracle Database 12c R1(PSR12.1.0.2 or later)/12c R2

  1. su - <Oracle user>

  2. Check that Oracle Restart started.

  3. srvctl enable asm

  4. srvctl start asm

  5. srvctl disable asm

Oracle ASM instance Shutdown

• Oracle Database 11g R2/12c R1(12.1.0.1)

  • Shutdown procedure of an Oracle ASM instance by user operation is as follows:

    1. su - <Oracle user>

    2. sqlplus /nolog

    3. connect / as sysasm

    4. shutdown <immediate / abort / transactional> (Setup with StopModeStop)
       Default : immediate

    5. If the Oracle ASM is not stopped at step "4" (except for abort), use shutdown abort.

    6. If the Oracle ASM is not stopped at step "4" or "5", shut it down forcibly by sending SIGKILL to the background processes.

  • Shutdown procedure of an Oracle ASM instance by resource failure or failover is as follows:

    1. su - <Oracle user>

    2. sqlplus /nolog

    3. connect / as sysasm

    4. shutdown <immediate / abort> (Setup with StopModeFail)
       Default : abort

    5. If the Oracle ASM is not stopped at step "4" (except for abort), use shutdown abort.

    6. If the Oracle ASM is not stopped at step "4" or "5", shut it down forcibly by sending SIGKILL to the background processes.

• Oracle Database 12c R1(PSR12.1.0.2 or later)/12c R2

  • Shutdown procedure of an Oracle ASM instance by user operation is as follows:

    1. su - <Oracle user>

    2. srvctl stop asm -stopoption <immediate/abort/transactional (Setup by "StopModeStop")> -force
       default : immediate

    3. If the Oracle ASM has not stopped in "2", execute the following.
       sqlplus /nolog
       connect / as sysasm
       shutdown <immediate/abort/transactional (Setup by "StopModeStop")>
       default : immediate

    4. If the Oracle ASM has not stopped in "3", execute the following. (When choosing excluding "abort" in "3")

       sqlplus /nolog

       connect / as sysasm

       shutdown abort

    5. If the Oracle ASM has not stopped in "3" or "4", abort the background process by sending SIGKILL.

  • Shutdown procedure of an Oracle ASM instance by resource failure or failover is as follows:

    1. su - <Oracle user>

    2. srvctl stop asm -stopoption <immediate/abort (Setup by "StopModeFail")> -force
       default : abort

    3. If the Oracle ASM has not stopped in "2", execute the following.
       sqlplus /nolog
       connect / as sysasm
       shutdown <immediate/abort (Setup by "StopModeFail ")>
       default : abort

    4. If the Oracle ASM has not stopped in "3", execute the following. (When choosing excluding "abort" in "3")
       sqlplus /nolog
       connect / as sysasm
       shutdown abort

    5. If the Oracle ASM has not stopped in "3" or "4", abort the background process by sending SIGKILL.