Oracle Startup routine startup parameter description _oracle

1. Start case without loading database
You can start a case without loading the database, typically before the database is created:
STARTUP Nomount

2. Start the case and mount the database
The user can start the case and mount the database without opening the database, allowing the user to perform a specific maintenance operation. For example:
L Rename the data file;
L Add, Undo, or rename redo log files;
L Start and disable redo log archiving;
L perform all database recoveries.
STARTUP MOUNT

3. Startup case mount and open database
The normal situation is when a case is started and the database is loaded and opened. This mode allows any valid user to connect to the database and perform a typical
Database access operation.
STARTUP

4. Restrict access to the database at startup
The user can start the case in strict mode and mount the database, which only allows the DBA to do the following:
L perform structural maintenance, such as rebuilding indexes;
L perform import and export of database files;
l Perform data loading;
• Temporarily block the use of data by typical users
STARTUP RESTRICT

5. Forcing the case to start
You can use the following command to force a case to start, and startup FORCE restarts if a case is starting.
STARTUP FORCE;

6. Start a case, mount the database, and start all media recovery
If the user requires media recovery, you can start a case, mount the database pointing to the case, and automatically start the recovery program.
STARTUP OPEN RECOVER;

7. Start exclusive or parallel mode
If a user's Oracle server allows multiple instances of concurrent access to a database (Oracle parallel server Option), you should select a single
Occupies or is loaded into a database in parallel.
For example:
STARTUP OPEN sale Pfile=initsale.ora PARALLEL;
If the user specifies exclusive (default), the database can only be loaded and opened by the current case. The following is a case of an exclusive pattern
：
Strartup OPEN Sales Pfile=initsales.ora execlusive RESTRICT
Other than that:
STARTUP [FORCE] [RESTRICT] [pfile= filename] [OPEN [recover][Database] | MOUNT | Nomount]
STARTUP Open:startup The default parameter is open, open the database, and allow access to the database. In the control file for the current instance
All of the files described are already open.

STARTUP Mount:mount Database, which only manages the DBA and does not allow users of the database to access it. Just the current instance
The control file is open and the data file is not open.

Startup nomount: Just initialize the file, assign the SGA area, start the database background process, not open control files and numbers
According to documents. Cannot access any database.

Startup pfile= FileName: Starts the database with filename as the initialization file, instead of using the default initialization file.
Startup FORCE: Aborts the current database operation and starts restarting the database normally.
STARTUP RESTRICT: Only users with restricted session permissions are allowed to access the database.
Startup RECOVER: The database starts and media recovery begins.
Shutdown has four parameters: NORMAL, transactional, IMMEDIATE, ABORT. The default is normal when no arguments are taken
。
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. Kai
No instance recovery is required when moving.

SHUTDOWN transactional: Do not allow new connections, do not wait for the session to end, wait for the transaction to end, make a checkpoint and close the number
According to documents. 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, make a checkpoint, and close the data
File. Transactions that do not end are automatically rollback. No instance recovery is required at startup.

SHUTDOWN ABORT: Do not allow new connections, do not wait for a session to end, do not wait for a transaction to end, do not do checkpoints, and do not close the data text
Thing Automatic instance recovery at startup.

In addition, the contents of normal, transactional, immediate,db Buffer cache were written to the data file, and no submitted
The transaction is rolled back, all resources are freed, and the database is "cleanly" closed.

The contents of the Abort,db Buffer cache were not written to the data file, and no transactions that were committed were rolled back. Database does not have
Dismount and shutdown, and data files are not closed. When the database is started, you need to recover the data through the redo log, by rolling back the segment to
The transaction is rolled back and the resource is freed.

---end----