Summary of Oracle Database startup and shutdown Methods

I. 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.

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, such as system tablespace or log files. Execute "nomount" and open the control file.

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

The following prompt appears when you enable the binding mode to start the database, but only allow users with certain privileges to access non-privileged users:

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 first, and then run the commands to start the database normally.

7. startup pfile = parameter file name

The startup method with the initialization parameter file first reads the parameter file, and then starts the database according to the settings in the parameter file.

Example: startup pfile = E: \ Oracle \ admin \ oradb \ pfile \ init. ora

8. startup EXCLUSIVE

PS: An error may be reported at startup: ORA-12514: TNS: The Listener currently cannot identify the Service requested in the connection descriptor, changed:

SQL> conn/as sysdba Already connected to the idle routine. SQL> startup mount The ORACLE routine has been started.

 

Ii. Closing methods:

1. Shut down the database normally.

2. shutdown immediate to immediately shut down the database.

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 closes the database directly. sessions that are 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.