Summary of several methods for disabling and starting Oracle

Summary of several methods for disabling and starting Oracle:
There are several startup methods:
1. startup nomount
Non-installation startup. In this mode, you can execute: re-build the control file and re-build the database.
 Read the init. ora file and start the instance, that is, start the SGA and background processes. To start the process, you only need the init. 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, data files and log files are not verified at this time.

3. startup open dbname
Run "nomount" first, then "mount", and then open all database files including the Redo log file,
 In this way, you can access data in the database.

4. startup
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
 Force start Mode
 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: OracleadminoradbpfileiniT. ora

8. startup EXCLUSIVE

There are three methods to disable the service:
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.