Oracle STARTUP routine STARTUP parameter description

Oracle STARTUP routine: STARTUP parameter description (2008-07-2820: 51: 20) label: startupshutdown case it classification: Oracle Data Management

Oracle STARTUP routine: startup parameter description (20:51:20) label: STARTUP shutdown case it classification: Oracle Data Management

1. Start the case without loading the database
You can start the instance without loading the database. This is generally done only when the database is created:
STARTUP NOMOUNT

2. Start the case and load the database
You can start the instance and mount it to the database without opening the database. This allows you to perform specific maintenance operations. For example:
L rename the data file;
L add, undo, or rename the redo log file;
L start and disable redo log archiving;
L perform all database recovery.
STARTUP MOUNT

3. Load and open the database by starting the instance
Normally, an instance is started, and the database is loaded and opened. This mode allows any valid user to connect to the database and perform typical
.
STARTUP

4. Restrict access to the database at startup
You can start an instance and load it into the database in strict mode. In this mode, only DBA is allowed to do the following:
L perform Structure Maintenance, such as re-indexing;
L import and export database files;
L execute data loading;
L temporarily stop typical users from using data
STARTUP RESTRICT

5. Force case initiation
You can use the following command to forcibly start an instance. If an instance is being started, startup force restarts.
Startup force;

6. Start an example, load the database, and start all media recovery.
If you require media recovery, you can start an instance, load the database pointing to the instance, and automatically start the recovery program.
Startup open recover;

7. Enable exclusive or parallel mode
If your ORACLE server allows multiple cases to concurrently access a database (Oracle Parallel Server option ),
Occupy or load the database in parallel.
For example:
Startup open sale PFILE = initsale. ora PARALLEL;
If you specify exclusive (default), the database can only be loaded and opened by the current instance. The following is an example of an exclusive mode.
:
Strartup open sales PFILE = initsales. ora EXECLUSIVE RESTRICT
In addition:
STARTUP [FORCE] [RESTRICT] [PFILE = filename] [OPEN [RECOVER] [database] | MOUNT | NOMOUNT]
Startup open: the default parameter of STARTUP is OPEN. OPEN the database and allow access to the database. In the control file of the current instance
All the files described have been opened.

Startup mount: MOUNT the database. only DBA is allowed to manage the database. Only the current instance
The control file is opened, and the data file is not opened.

Startup nomount: only through the initialization file, allocate the SGA area, start the database background process, did not open the control file and
Data file. You cannot access any database.

Startup pfile = filename: Start the database with filename as the initialization file, instead of using the default initialization file.
Startup force: Stop the running of the current database and restart the database.
Startup restrict: only users with restricted session permission can access the database.
Startup recover: starts the database and starts media recovery.
SHUTDOWN has four parameters: NORMAL, TRANSACTIONAL, IMMEDIATE, and ABORT. The default value is NORMAL if no parameter is included.
.
Shutdown normal: do not allow new connections, wait for the session to end, wait for the transaction to end, make a checkpoint, and close the data file. Qi
You do not need to recover the instance when the instance is running.

Shutdown transactional: does not allow new connections, does not wait for the session to end, waits for the transaction to end, makes a checkpoint and closes the number
Data file. No instance recovery is required at startup.

Shutdown immediate: do not allow new connections, do not wait for the session to end, do not wait for the transaction to end, do a checkpoint and close the data
File. Transactions that are not finished are automatically rolled back. No instance recovery is required at startup.

Shutdown abort: does not allow new connections, does not wait for the session to end, does not wait for the transaction to end, does not do the checkpoint and does not close the data file
. The instance is automatically restored at startup.

In addition, for NORMAL, TRANSACTIONAL, IMMEDIATE, DB Buffer Cache content is written into the data file, not submitted
The transaction is rolled back, all resources are released, and the database is "clean.

For ABORT, the content of the DB Buffer Cache is not written into the data file, and transactions that are not committed are not rolled back. Database not
Dismount and close, and the data file is not closed. When the database is started, you must use the redo log to restore data and use the rollback segment
The transaction is rolled back to release the resource.

--- End ----