Oracle Database startup and shutdown Methods
I. Several startup methods:
1. startup nomount is not installed and started. In this mode, execute the following commands: re-build the control file and re-build the database.
Start the instance, that is, start the SGA and background processes. To start the instance, you only need the init. ora file.
2. startup mount dbname
Install and start. In this mode, you can execute: Database Log archiving, database recovery, and renaming some database files.
Execute "nomount" and open the control file.
3. startup open dbname: Execute "nomount", 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 Constraints
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
When the database cannot be closed, you can use startup force to close the database.
Shut down the database first, and then execute the normal database startup command
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
Ii. Closing methods:
1. shutdown normal
Close the database normally.
2. shutdown immediate
Close the database immediately.
Run shutdown immediate in SVRMGRL, and the database is not closed immediately,
However, it is disabled only after Oracle executes some cleanup tasks (terminating sessions and releasing session resources ),
When you use shutdown to close a database, shutdown immediate can be used to close the database.
3. shutdown abort
Directly shut down the database, and the session accessing the database will be suddenly terminated,
If a large number of operations are being performed in the database, it takes a long time to restart the database after the shutdown abort command is executed.