1.It is a small binary file.2.Defines current state of physical database.3.Maintains integrity of database4.Required
At mount state during databse startup to operate the database.5.Linked to a single database.6.Incase of loss may required recovery.7.Sized initially by create database.
SIZING CONTROL FILE:
1.MAXLOGFILES= Maximum number of logfile can be ever created for thedatabase.2.MAXLOGMEMBERS= Maximum number of logfile members can be evercreated for the database.3.MAXLOGHISTORY= Maximum of the archived redo log file for automaticmedia recovery of the Oracle Real Application Clusters.4.MAXDATAFILE= Maximum number of data files can be ever created for thedatabase.
An attempt to add a new file whose number is greater thanMAXDATAFILES, but less than or equal to DB_FILES, causes the control fileexpand.
INFORMATIONS IN CONTROL FILE:
1.Database name (taken from parameter DB_NAME or from CREATEDATABASE).2.Database identifier is recorded when the database is created.3.Timestamp of database creation.4.Names & location of datafiles & online redolog files. Updated if they areadded, renamed or dropped.5.Tablespace information is updated as tablespace are added or dropped.6.Location & status of archived logs.7.Location & status of backup.8.Current log sequence number is recorded when log switcher occurs.9.Checkpoint information is recorded as checkpoint made. The control file consists of two types of sections1.Reusable2.Not reusable.Reusable section store RMAN information of backup & can be reused by RMANonly.
MULTIPLEXING THE CONTROL FILES:
It can be multiplexed up to 8 times.