1. startup nomount
For non-installation startup, execute re-build the control file and re-build the database to read init. ora file, start the instance, that is, start the SGA and background processes. ora file.
2. startup Mount dbname
Install and start. In this mode, run:
Database Log archiving,
Database media recovery,
Online or offline data files,
Locate the data file and redo the log file.
Execute "nomount", open the control file, and confirm the location of the data file and the on-line log file. However, the data file and log file are not verified at this time.
3. startup open dbname
Run "nomount" first, then "Mount", and then open all database files including redo log files. In this way, you can access data in the database.
4. startup, which is equal to the following three commands
Startup nomount
Alter database Mount
Alter database open
5. startup restrict
Constraint-based startup
This method can start the database, but only allow access by users with certain privileges
When a non-authorized user accesses the service, the following prompt is displayed:
Error:
ORA-01035: Oracle only allows users with restricted session Permissions
6. startup force
Forced start mode. When the database cannot be closed, you can use startup force to close the database. First, close the database and then execute the commands to start the database normally.
7. startup pfile = parameter file name
Startup method with initialization parameter file
Read the parameter file first, and then start the database according to the settings in the parameter file.
Example: startup pfile = E:/Oracle/admin/oradb/pfile/init. ora
8. startup exclusive