CF, Controlfile Transaction
How Many Resources:
2: 1 to serialize controlfile transactions, 1 to serialize reads and writes from shared information portion
of controlfile, which is a special global notepad area of the controlfile.
How Many Locks:
1 Lock for each process that tries to perform a Control File operation.
How Many Users:
(depends)
Who Uses:
Any foreground or background doing a controlfile transaction
When Used:
- switching logfiles, held exclusive.
- updating checkpoint information for datafiles, held exclusive.
- opening a logfile for redo reading during recovery, held shared.
- getting information to perform archiving, held shared.
- performing crash recovery, held exclusive.
- performing instance recovery, held exclusive.
- performing media recovery, held exclusive.
- dumping logfile history, held shared.
- updating archiving information, then exclusive.
- creating a database, held exclusive.
- mounting a database, held shared.
- closing a database, held shared.
- adding a logfile or logfile member, held exclusive.
- dropping a logfile or logfile member, held exclusive.
- checking information about logfile group members, held shared.
- adding a new datafile, held exclusive.
- dropping a datafile, held exclusive.
- re-creating (as empty) an existing database file, held shared to find the file, held exclusive to perform
the update to the file entry in the controlfile when the zeroing task is complete.
- identifying or re-identifying database files, held shared.
- setting a set of datafiles OFFLINE, held exclusive twice in a two step process.
- setting a set of datafiles ONLINE, held exclusive, and then again when the transaction subsystem
completes applying save undo to the on-lined files, a two-step process.
- marking a set of datafiles READONLY, held exclusive twice in a two-step process.
- marking a set of READONLY datafiles READWRITE, held exclusive twice in a two-step process.
- formatting a new controlfile, i.e. CREATE CONTROLFILE, held exclusive.
- beginning a hot backup, held exclusive.
- ending a hot backup, held exclusive.
- checking to see, after a crash, whether datafiles are in hot backup mode, held shared, then exclusive.
- executing a ALTER DATABASE BACKUP CONTROLFILE TO TRACE, held shared.
- opening the database (controlfile), held exclusive by first instance to open, shared by subsequent
instances.
- renaming datafiles or logfiles, held exclusive.
- marking a controlfile as valid and mountable, held exclusive.
- handling an error encountered in the controlfile, held exclusive.
- validating data dictionary entries against matching controlfile records for file entries, held exclusive.
- updating controlfile format after a software upgrade, held exclusive.
- scanning for log file info by log sequence #, held shared.
- finding the highest-in-use entry of a particular controlfile record type, held shared.
- getting information about the number of log entries and their lowest/highest sequence number and
log file numbers, held shared.
- looking up a controlfile record matching a given filename, held shared.
- retrieving or updating a controlfile record, held shared for retrieval, exclusive for update.
- making a backup controlfile, held exclusive for the duration of the copy.
- dumping the contents of the controlfile during debugging, held shared.
- dumping contents of a current redo logfile during debugging, held shared.
- dumping contents of redo log headers, held shared.
- dumping contents of datafile headers, held shared.
- updating MAC security mode in Trusted Oracle, held exclusive.
- reading shared information from the controlfile, held exclusive until shared information is written
back updated, or done looking at it. Shared information is read and updated infrequently and is
used primarily for instances to agree on compatibility, modes of operation, and for system commit
number housecleaning in instance recovery situations.
Id1, Id2 Combinations:
TABLE 20. Id1, Id2 Combinations for CF Resource.
Id1 Id2 Meaning
0 0 Serialize Control file actions
0 1 Shared Information Access.
Init.ora parameters:
processes
Scope:
Local, Global.
Operation:
Synchronous.