Oracle Database Startup and Close
First, several start-up mode:
1. Startup Nomount is not installed, this way is started: rebuild the control file, rebuild the database launch instance, which starts the SGA and the background process, this startup only needs the init.ora file. 2, startup mount dbname installation start, this way can be performed: Database log archive, database recovery, renamed some database files such as: system table space or log file. Perform "Nomount", then open the control file 3, startup open dbname Execute "Nomount" first, then execute "mount", open all database files including the Redo log file, this mode can access the data in the database. 4, startup, equal to the following three commands Startup Nomount ALTER DATABASE MOUNT ALTER DATABASE OPEN 5, STARTUP RESTRIC TRABASE OPEN 5, Startup Restrict Constraint Mode Starting this method can start the database, but only the user has access to non-privileged user access, the following prompts will occur when accessing non-privileged users : Error: ORA-01035: Oracle only allows users with Restricted session privileges to use 6, Startup Force enforcement mode When the database cannot be turned off, you can use Startup force to complete the database to complete the database, then execute the normal boot database command 7 , Startup pfile = Parameter file name The startup method of the initialization parameter file first reads the parameter file, then start the database example by setting the settings in the parameter file: Startup Pfile = E: /Oracle/admin/oradb/pfile/init.ora 8, Startup Exclusive
Second, several closed methods:
1. Shutdown Normal is normal to close the database. 2, shutdown immediate turns off the database immediately. Execute Shutdown Immediate in SVRMGRL, the database does not turn off immediately, but is turned off after Oracle executes some cleared work (terminating session, release session resources), when using shutdown, Shutdown Immediate can complete the database shutdown . 3, Shutdown Abort directly closes the database, the session that is accessing the database will be suddenly terminated, if there is a lot of operation in the database is being executed, then after Shutdown Abort, restart the database take a long time.
