开启数据库的三个状态

Starting Up a Database
When starting the database, you select the state in which it starts. The following scenarios describe different stages of starting up an instance.
Starting the Instance (NOMOUNT)
An instance would be started in the NOMOUNT stage only during database creation or the re-creation of control files.
Starting an instance includes the following tasks:
  • Reading the initialization file from $ORACLE_HOME/dbs in the following order:
    - First spfileSID.ora
    - If not found then, spfile.ora
    - If not found then, initSID.ora
Specifying the PFILE parameter with STARTUP overrides the default behavior.
  • Allocating the SGA
  • Starting the background processes
  • Opening the alertSID.log file and the trace files
The database must be named with the DB_NAME parameter either in the initialization parameter file or in the STARTUP command.
 
Mounting the Database (MOUNT)
To perform specific maintenance operations, you start an instance and mount a database but do not open the database.
For example, the database must be mounted but not open during the following tasks:
  • Renaming data files
  • Enabling and disabling online redo log file archiving options
  • Performing full database recovery
Mounting a database includes the following tasks:
  • Associating a database with a previously started instance
  • Locating and opening the control files specified in the parameter file
  • Reading the control files to obtain the names and status of the data files and online
redo log files. However, no checks are performed to verify the existence of the data files and online redo log files at this time.
 
Opening the Database (OPEN)
Normal database operation means that an instance is started and the database is mounted and open. With normal database operation, any valid user can connect to the database and perform typical data access operations.
Opening the database includes the following tasks:
  • Opening the online data files
  • Opening the online redo log files
If any of the data files or online redo log files are not present when you attempt to open the
database, the Oracle server returns an error.
During this final stage, the Oracle server verifies that all the data files and online redo log
files can be opened and checks the consistency of the database. If necessary, the SMON
background process initiates instance recovery.