|SQL*Plus User's Guide and Reference
Part Number A90842-01
This chapter provides a brief overview of the database administration tools available in SQL*Plus, and discusses the following topics:
This chapter is intended for use by database administrators. In order to access the functionality of the commands mentioned in this chapter, database administrator privileges are necessary.
For more information on database administration, see the Oracle9i Database Concepts manual.
Special operations such as starting up or shutting down a database are performed by a database administrator (DBA). The DBA has certain privileges that are not assigned to normal users. The commands outlined in this chapter would normally be used by a DBA.
For more information about security and roles in SQL*Plus, see Chapter 10, "SQL*Plus Security".
An Oracle database may not always be available to all users. To open or close a database, or to start up or shut down an instance, you must have DBA privileges or be connected as SYSOPER or SYSDBA. Other users cannot change the current status of an Oracle database.
You cannot use STARTUP or SHUTDOWN to start or stop Oracle instances on Oracle7 servers.
Starting a database involves three steps:
An instance controls the background processes and the allocation of memory area to access an Oracle database.
Mounting the database associates it with a previously started instance.
Opening the database makes it available for normal database operations.
To start an Oracle instance, without mounting the database, enter
To start an instance, mount the database, but leave the database closed, enter
To start an instance using the Oracle9i Server parameter file INITSALE.ORA, mount and open the database named SALES in exclusive mode, and restrict access to administrative personnel, enter
where SALES is the database name specified in the DB_NAME parameter in the INITSALE.ORA parameter file.
Shutting down a database involves three steps:
When a database is closed, all database and recovery data in the SGA are written to the datafiles and redo log files, and closes all online datafiles.
Dismounting the database disassociates the database from an instance and closes the control files of the database.
Shutting down an instance reclaims the SGA from memory and terminates the background Oracle processes that constitute an Oracle instance.
To shut down the database normally after it has been opened and mounted, enter
Every Oracle database has a set of two or more redo log files. The set of redo log files for a database is collectively referred to as the database's redo log.
The redo log is used to record changes made to data. If, for example, there is a database failure, the redo log is used to recover the database. To protect against a failure involving the redo log itself, Oracle allows a mirrored redo log so that two or more copies of the redo log can be maintained on different disks.
Operating a database in ARCHIVELOG mode enables the archiving of the online redo log.
The ARCHIVE LOG command permits a complete recovery from disk failure as well as instance failure, because all changes made to the database are permanently saved in an archived redo log.
For more information about redo log files and database archiving modes, see the Oracle9i Database Concepts manual. For information about using the ARCHIVE LOG command, see Chapter 13, "SQL*Plus Command Reference".
To automatically begin archiving, enter
To list the details of the current log file being archived, enter
ARCHIVE LOG LIST
Database log mode Archive Mode Automatic archival Enabled Archive destination /vobs/oracle/dbs/arch Oldest online log sequence 221 Next log sequence to archive 222 Current log sequence 222
If a damaged database is in ARCHIVELOG mode, it is a candidate for either complete media recovery or incomplete media recovery operations. To begin media recovery operations use the RECOVER command. For more information about using the RECOVER command, see Chapter 13, "SQL*Plus Command Reference".
In order to begin recovery operations, you must have DBA privileges.
To recover the database up to a specified time using a control backup file, enter
To recover two offline table-spaces, enter
Make sure that the table-spaces you are interested in recovering have been taken offline, before proceeding with recovery for those table-spaces.