|Oracle8i Recovery Manager User's Guide and Reference
Release 2 (8.1.6)
Part Number A76990-01
Recovery Manager Command Syntax, 44 of 50
To shut down the target database without exiting RMAN. This command is equivalent to using the SQL*Plus SHUTDOWN statement.
- Execute this command at the RMAN prompt or within the braces of a run command.
- You cannot use the RMAN shutdown command to shut down the recovery catalog database. To shut down this database, start a SQL*Plus session and issue a SHUTDOWN statement.
- The normal, transactional, and immediate options all perform a clean close of the database. The abort option does not cleanly close the database; Oracle will perform instance recovery at startup.
- If your database operates in NOARCHIVELOG mode, then you must shut down the database cleanly and then issue a startup mount before a making a backup.
Keywords and Parameters
shuts down the database with normal priority (default option), which means:
- No new connections are allowed after the statement is issued.
- Before the database is shut down, Oracle waits for all currently connected users to disconnect from the database.
- The next startup of the database will not require instance recovery.
aborts the target instance, with the following consequences:
- All current client SQL statements are immediately terminated.
- Uncommitted transactions are not rolled back until next startup.
- Oracle disconnects all connected users.
- Oracle will perform crash recovery on the database at next startup.
shuts down the target database immediately, with the following consequences:
- Current client SQL statements being processed by Oracle are allowed to complete.
- Uncommitted transactions are rolled back.
- All connected users are disconnected.
shuts down the target database while minimizing interruption to clients, with the following consequences:
- Clients currently conducting transactions are allowed to complete, that is, either commit or abort before shutdown.
- No client can start a new transaction on this instance; any client attempting to start a new transaction is disconnected.
- After all transactions have either committed or aborted, any client still connected is disconnected.
Shutting Down a Database in Immediate Mode
This example waits for current SQL transactions to be processed before shutting down, then mounts the database:
Shutting Down a Database in NOARCHIVELOG Mode
This example backs up a database running in NOARCHIVELOG mode:
# executing the above commands ensures that database is in proper state for noarchivelog
set duplex = 4;
allocate channel dev1 type 'sbt_tape';
alter database open;