Oracle Server Manager User's Guide

STARTUP

Purpose

Start an Oracle instance with several options, including mounting and opening a database.

Prerequisites

You must be connected to a database as INTERNAL, SYSOPER, or SYSDBA. You cannot be connected via a multi-threaded server.

Syntax

STARTUP command ::=

MOUNT_OPTIONS clause ::=

where:

FORCE Shuts down the current Oracle instance (if it is running) with SHUTDOWN mode ABORT, before restarting it. If the current instance is running and FORCE is not specified, an error results. FORCE is useful while debugging and under abnormal circumstances. It should not normally be used.
RESTRICT Only allows Oracle users with the RESTRICTED SESSION system privilege to connect to the database . Later, you can use the ALTER SYSTEM command to disable the restricted session feature.
PFILE=filename Causes the specified parameter file to be used while starting up the instance.
MOUNT Mounts a database but does not open it.
OPEN Mounts and opens the specified database.
NOMOUNT Causes the database not to be mounted upon instance startup. Cannot be used with SHARED, EXCLUSIVE, PARALLEL, MOUNT, or OPEN.
RECOVER Specifies that media recovery should be performed, if necessary, before starting the instance. STARTUP RECOVER has the same effect as issuing the RECOVER DATABASE command and starting an instance. Only complete recovery is possible with the RECOVER option.
Recovery proceeds, if necessary, as if AUTORECOVERY is set to ON, regardless of whether or not AUTORECOVERY is enabled. If a redo log file is not found in the expected location, recovery continues as if AUTORECOVERY is disabled, by prompting you with the suggested location and name of the subsequent log files that need to be applied. See "Usage Notes" in "RECOVER" for a description of how to proceed with recovery when AUTORECOVERY is disabled.
If recovery fails using the RECOVER option, the database remains mounted and closed.
database The name of the database to mount or open. If no database name is specified, the database name is taken from the initialization parameter DB_NAME.
EXCLUSIVE Signifies that the database can only be mounted and opened by the current instance (it cannot be opened simultaneously by multiple instances). Cannot be used with SHARED, PARALLEL, or NOMOUNT. If no mounting option is specified, EXCLUSIVE is assigned by default.
PARALLEL Must be specified if the database is to be mounted by multiple instances concurrently. Cannot be used with EXCLUSIVE or NOMOUNT. Invalid if the initialization parameter SINGLE_PROCESS is set to TRUE.
SHARED Synonym for PARALLEL.
RETRY Specifies that opening the database should be attempted every five seconds if the instance is busy being recovered by another instance. When an instance is being recovered by another instance, the down instance cannot open the database until recovery is complete. If the database cannot be opened for any other reason, RETRY does not attempt to open the database again. This option is only available for instances operating in PARALLEL mode. The number of times RETRY attempts to start the database can be set with the SET RETRIES command (see "RETRIES" in "SET" ).

Examples

To start an instance using the standard parameter file, mount the default database in exclusive mode, and open the database, enter:

STARTUP

or enter:

STARTUP OPEN databasename EXCLUSIVE

To start an instance using the standard parameter file, mount the default database in parallel mode, and open the database, enter:

STARTUP PARALLEL

STARTUP OPEN databasename PARALLEL

To restart an instance that went down in parallel mode and may not yet have been recovered by other instances, use the RETRY option:

STARTUP PARALLEL RETRY

To shut down the current instance, immediately restart it without mounting or opening, and allow only database administrators to connect, enter:

STARTUP FORCE NOMOUNT RESTRICT

To start an instance using the parameter file TESTPARM without mounting the database, enter:

STARTUP PFILE=testparm NOMOUNT

To shut down a particular database, immediately restart and open it in parallel mode, allow access only to database administrators, and use the parameter file MYINIT.ORA. enter:

STARTUP OPEN databasename PFILE=myinit.ora FORCE SHARED RESTRICT

To start up an instance and mount but not open a database, you can use the following sequence of commands (the system's response is also shown):

CONNECT INTERNAL

Connected.

STARTUP NOMOUNT

Oracle instance started.

ALTER DATABASE MOUNT

Statement processed.

At this point, you could run a maintenance command and then open the database, as shown in the following commands:

ALTER DATABASE ARCHIVELOG;

Statement processed.

ALTER DATABASE OPEN;

Statement processed.

FORCE	Shuts down the current Oracle instance (if it is running) with SHUTDOWN mode ABORT, before restarting it. If the current instance is running and FORCE is not specified, an error results. FORCE is useful while debugging and under abnormal circumstances. It should not normally be used.
RESTRICT	Only allows Oracle users with the RESTRICTED SESSION system privilege to connect to the database . Later, you can use the ALTER SYSTEM command to disable the restricted session feature.
PFILE=filename	Causes the specified parameter file to be used while starting up the instance.
MOUNT	Mounts a database but does not open it.
OPEN	Mounts and opens the specified database.
NOMOUNT	Causes the database not to be mounted upon instance startup. Cannot be used with SHARED, EXCLUSIVE, PARALLEL, MOUNT, or OPEN.
RECOVER	Specifies that media recovery should be performed, if necessary, before starting the instance. STARTUP RECOVER has the same effect as issuing the RECOVER DATABASE command and starting an instance. Only complete recovery is possible with the RECOVER option.
	Recovery proceeds, if necessary, as if AUTORECOVERY is set to ON, regardless of whether or not AUTORECOVERY is enabled. If a redo log file is not found in the expected location, recovery continues as if AUTORECOVERY is disabled, by prompting you with the suggested location and name of the subsequent log files that need to be applied. See "Usage Notes" in "RECOVER" for a description of how to proceed with recovery when AUTORECOVERY is disabled.
	If recovery fails using the RECOVER option, the database remains mounted and closed.
database	The name of the database to mount or open. If no database name is specified, the database name is taken from the initialization parameter DB_NAME.
EXCLUSIVE	Signifies that the database can only be mounted and opened by the current instance (it cannot be opened simultaneously by multiple instances). Cannot be used with SHARED, PARALLEL, or NOMOUNT. If no mounting option is specified, EXCLUSIVE is assigned by default.
PARALLEL	Must be specified if the database is to be mounted by multiple instances concurrently. Cannot be used with EXCLUSIVE or NOMOUNT. Invalid if the initialization parameter SINGLE_PROCESS is set to TRUE.
SHARED	Synonym for PARALLEL.
RETRY	Specifies that opening the database should be attempted every five seconds if the instance is busy being recovered by another instance. When an instance is being recovered by another instance, the down instance cannot open the database until recovery is complete. If the database cannot be opened for any other reason, RETRY does not attempt to open the database again. This option is only available for instances operating in PARALLEL mode. The number of times RETRY attempts to start the database can be set with the SET RETRIES command (see "RETRIES" in "SET" ).