These records contain noncritical information that is eligible to be overwritten if needed. When all available record slots are full, the database either expands the control file to make room for a new record or overwrites the oldest record. Examples include records about:.
Most of the reusable section of the control file contains RMAN backup information. If you want to change the name of the database, we need to recreate the control file by generating a text-based control file by executing the following command. The above command creates a text-based control file either in udump directory or trace directory. Also read, Controlfile management activity. Thank you for giving your valuable time to read the above information. I hope the content served your purpose in reaching out the blog.
Suggestions for improvement of the blog are highly appreciable. We need to change a hard limit database parameter in the control file. If we are moving our database to another server, our files are present in different locations. Oracle customer support advises us to do so. For recreating the control file, we need to follow the below steps:. The above command creates one trace file in a trace directory location. To know the trace directory, we need to fire the following command.
If it is 10g database: The trace file store in a dump location. Now shut down the database and copy the most recent trace file to the oracle user home directory or some other location with a different name and extension must and should be. Now move to the trace directory by using the following command. Search the recent trace file that contains the extension with cricket. Now remove the existing control file that is related to cricket database.
Move to that directory location and remove the existing control files. Now, start up the database at nomount state and run the edited trace file i.
After running the file, we need to open the database by using resetlogs option by using the following command. Then, we need to add the temporary files for existing temporary tablespaces by using the following command. Here my temporary tablespace is tempts.
This section describes ways to create control files, and contains the following topics:. The size of the control file changes between some releases of Oracle, as well as when the number of files specified in the control file changes.
Your operating system specific Oracle documentation contains more information about specifying control files. You can create an an additional control file copy by copying an existing control file to a new location and adding the file's name to the list of control files. Similarly, you rename an existing control file by copying the file to its new name or location, and changing the file's name in the control file list.
In both cases, to guarantee that control files do not change during the procedure, shut down the instance before copying the control file. For example, you would change a database's name if it conflicted with another database's name in a distributed environment. The following statement creates a new control file for the prod database formerly a database that used a different database name :.
If you follow recommendations for control file backups as discussed in "Backing Up Control Files" , you will already have a list of datafiles and online redo log files that reflect the current structure of the database. However, if you have no such list, executing the following statements will produce one. If you have no such lists and your control file has been damaged so that the database cannot be opened, try to locate all of the datafiles and online redo log files that constitute the database.
Any files not specified in Step 5 are not recoverable once a new control file has been created. Moreover, if you omit any of the files that make up the SYSTEM tablespace, you might not be able to recover the database. If the database is open, shut down the database normally if possible. In this case, you will need to recover from the loss of the redo logs Step 8. If you are creating the control file as part of recovery, recover the database.
If you have lost online or archived redo logs or datafiles, use the procedures for recovering those files. This section describes the most common control file usage errors, and contains the following topics:. After creating a new control file and using it to open the database, check the alert file to see if Oracle has detected inconsistencies between the data dictionary and the control file, such as a datafile that the data dictionary includes but the control file does not list.
If a datafile exists in the data dictionary but not in the new control file, Oracle creates a placeholder entry in the control file under the name MISSING nnnn where nnnn is the file number in decimal. In this case, you must drop the tablespace containing the datafile. In contrast, if a datafile indicated in the control file is not present in the data dictionary, Oracle removes references to it from the new control file. In both cases, Oracle includes an explanatory message in the alert.
In this case, you should restore the files you backed up in Step 3 and repeat the procedure from Step 4 , using the correct filenames. You have two options:.
0コメント