1. Open the database
Ø Startup routine
Read parameter file inInt.ora
Assign SGA
Start the background process
Open alert file and track file
Ø Load database
For example, in the following tasks, you must load the database but don't open the database.
Named data file
Enable and disable redo log archiving options
Perform full database recovery
The loading database includes the following tasks
Enclose the database with the previously started routine
Locate and open the control file specified in the parameter file
Read the control file to get the name and status of the data file and redo the log file, but do not perform the inspection of the data file and online redo log files.
Ø Open the database
Turn on online data file
Open online log file
In this final phase, the Oracle server verifies whether all data files and online redo log files are open and check the consistency of the database. If necessary, the system monitor background process (SMON) startup routine is restored, the front roll to recover the data in the data file but has recorded in the online redo log, open the database instead of waiting for the retreat of all transactions The database can be used immediately when the unrecovered transaction lock is available, and when the SMON and each server process accesses the locked data, returning to the uncommitted transaction
Ø Command: Startup
Startup [force] [restrict] [Pfile = filename]
[Open [Recover] | MOUNT | NOMOUNT]
Note: This is not a complete syntax
Open: User Access Database
Mount: Load the database for some DBA lives but not allow users to access the database
Nomount: Create SGA and start the background process but not allow access to the database
Pfile = parfilename: Allows the use of non-default parameter file configuration routines
FORCE: Running Run before performing normal startup
Restrict: Users with RESTRICTED SESSION permissions allow access databases
Recover: Start the media recovery when starting the database
2, turn off the database
Ø Close the database
Oracle Server writes the entries in the Buffer Cache and the entries in the Redo log buffer cache to data files and online redo log files
Oracle Server Turn off all online data files and online redo log files
Ø Unloading database
Oracle server closes its control file
Ø Closed routine
Alert files and trace files will be closed, and SGA is reclaimed and the background process is terminated.
Ø Command: shutdown
Shutdown [Normal | Transactional | Immediate | Abort]
Close mode a i t n
New connection, X x x x
Wait until the current session ends X x x 0
Wait until the end of the current business X x 0 0
Perform checkpoints and close file x 0 0 0
Normal (default):
No new connection
Oracle server waits for all users to complete the shutdown
Oracle will turn off and unload the database before closing the routine
The next time the routine recovery will not be required.
Transactional --- Prevent customers from being lost
No customers can start new transactions in this particular routine
Disconnect the customer when the customer ends ongoing transaction
When all transactions have been completed, turn off immediately
The next startup will not require routine recovery
Immediate
The current SQL statement processed by Oracle is not completed
Oracle server does not wait for the user disconnected by the current connection database
Oracle retreats transactions and disconnect all connections
Oracle will turn off and unload the database before closing the routine
The next startup will not require routine recovery
Abort
The current SQL statement processed by the Oracle server is immediately terminated.
Oracle does not wait for the user disconnected by the current connection database
Unintered transactions do not return
In the case where the file is not closed, the routine is terminated.
The next startup will require routine recovery
Ø NT via registration customs database
Stop OraclesIDesid service, also terminate ORACLESTARTSID, and execute ORASHUT.BAT scripts
