Oracle Database startup and shutdown Methods

This article describes how to start and shut down an Oracle database. For more information, see start data $ sqlplussyspassassysdbasqlstartup. 2. If the listener process is not started after the listener database is started, the client cannot connect to the database. The start method of the listening process is: $ lsnrctlstart at wid

This article mainly introduces the Oracle database startup and shutdown methods. For more information, see $ sqlplus sys/pass as sysdba sqlstartup. 2. After starting the listener database, if the listening process is not started, the client cannot connect to the database. The start method of the listening process is: $ lsnrctl start at wid

This article mainly introduces the Oracle database startup and shutdown methods. For more information, see

I. Start data

$ Sqlplus "sys/pass as sysdba"
SQL> startup

Ii. Start the listener

After the database is started, if the listening process is not started, the client cannot connect to the database. The method for starting a listening process is as follows:
$ Lsnrctl start
In widnows, listeners can be started from the service list.
The listening mileage configuration file is listener. ora, which is located in the/home/app/oracle/product/10.1.0/db1/network/admin/directory /.
This configuration file is divided into two parts, one is the configuration of the listener itself, including the protocol, address, port number, and the other is the instance information of the database connected to the listener, including: instance name, global database name, and oracle Home Directory. Listeners can be configured using the oracle net config wizard.
To display the running status of the listener: $ lsnrctl status;
To stop the listener: $ lsnrctl stop.

Iii. Database Startup Process

There are three phases:
1. Start the instance, including the following operations:
1) read the parameter file
2) SGA allocation
3) Start the background process
2. Load the database
The database is loaded to associate the database with the started instance. After the database is loaded, the database remains closed.
3. Open the database
In this step, the database can be used for normal operations. Open Control Files, database files, and log files.

Iv. Database startup parameters

1. NOMOUNT: only start the instance, not load the database
SQL> startup nomount
2. MOUNT: Start the instance and load data, but do not open the database
SQL> startup mount
3. read only: Set the database to READ-ONLY
SQL> startup mount
SQL> alter database open read only
4. read write: Open Data in READ/WRITE mode. This is the default mode.
SQL> startup mount
SQL> alter database open read write
5. OPEN: OPEN the database. This is the default method.
SQL> startup mount
SQL> alter database open;
6. RESTRICT: only users with restricted session permission can access the database.
SQL> startup restrict
7. PFILE: Specify the parameter file at startup
SQL> startup pfile =/u02/user/mypfile. ora
8. FORCE: Start the database forcibly.
SQL> startup pfile =/u02/user/mypfile. ora open restrict force

5. Database Shutdown

As opposed to the startup process, closing involves three processes.
1). Shut down the database
2). Uninstall the database
3). Shut down the database instance

1. NORMAL Close Mode
The NORMAL closing mode is the NORMAL closing mode, which is the default closing mode. In this mode, the database server can shut down the database only after all clients exit from Oracle normally.
SQL> SHUTDOWN NORMAL
2. IMMEDIATE close Method
When you close a database in this way, the system rolls back all transactions that have not been committed by all users connected to the database, interrupts the connection, and closes the database.
SQL> SHUTDOWN IMMEDIATE
3. ABORT close Method
ABORT closes the database in an abnormal way. When the database is closed in this way, the system immediately closes the database instance and does not check the data integrity of the transaction chamber. Is the fastest way to shut down.
SQL> shutdown abort;
4. Disable TRANSACTIONAL
In this shutdown mode, the database must wait for all the clients to end the transaction, submit or roll back.
SQL> shutdown transactional

5. SQL> startup force start

6. oracle disables archivelog
SQL> shutdown immediate;
SQL> alter database noarchivelog; (archivelog) Disable enabling
SQL> alter database open;
Or change the parameters in pfile/spfile:
Log_archive_start = true restart the database or execute: archive log start Enables automatic archiving of the database, but the database is still in manual archiving mode after restart.