Name

CREATE CONTROLFILE

Synopsis

CREATE CONTROLFILE [REUSE] [SET] 
        DATABASE database_name
        {LOGFILE {[GROUP integer] filename}...}
        [RESETLOGS | NORESETLOGS]
        [DATAFILE filename]
        [MAXLOGFILES integer]
        [MAXLOGMEMBERS integer]
        [MAXLOGHISTORY integer]
        [MAXDATAFILES integer]
        [MAXINSTANCES integer]
        [ARCHIVELOG | NOARCHIVELOG]
        [CHARACTER SET character_set]

SQL*Plus command. Allows you to re-create the control file. You can create the control file by manually entering the values for the control file or by using the text file created with a previous BACKUP CONTROLFILE TO TRACE command.

For any parameters for which you don’t specify values with the CREATE CONTROLFILE statement, Oracle will use the default values for the parameters.

Keywords

REUSE

Causes the control file named in the CONTROL_FILE initialization parameter to become the new control file. If the control file named in the initialization file exists and the REUSE keyword is not used, an error will be returned.

SET

Indicates that the database_name is the new name for the database.

DATABASE database_name

Specifies the name of the database for the control file.

LOGFILE filename

Specifies the name of the log file to be used for the database. You must list all members of all redo log groups.

GROUP integer

Specifies the number of the log file group.

RESETLOGS | NORESETLOGS

Indicates whether the database should ignore any log files listed for the log file clause. These keywords are used to prevent log file conflicts in the event of an incomplete recovery. ...

Get Oracle in a Nutshell now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.