\uc774\uc804 database\uc5d0\uc11c control file\uc758 trace \ubcf8\uc744 \ubc31\uc5c5\ubc1b\uc740 \ud6c4 \ud574\ub2f9 \ud30c\uc77c\uc744 \uc815\ub9ac\ud558\uba74 \uc0c8\ub85c\uc6b4 control file\uc744 \uc0dd\uc131\ud558\ub294 \uc2a4\ud06c\ub9bd\ud2b8\ub97c \uc0dd\uc131\ud560 \uc218 \uc788\ub2e4.<\/p>\n
— Cron modify<\/p>\n
— lsnrctl stop<\/p>\n
script ReCre_Controlfile.log<\/p>\n
shutdown immediate<\/p>\n
startup<\/p>\n
alter database backup controlfile to trace ;<\/p>\n
alter database backup controlfile to ‘\/ol0_orah01\/oracle\/adm\/P01OL1\/udump\/CTRL20020916_Before’ ;<\/p>\n
shutdown<\/p>\n
startup nomount mv \/ol0_orah01\/ORACLE\/P01OL1\/ctl\/cntrlP01OL1805_1.dbf \/ol0_orah01\/ORACLE\/P01OL1\/ctl\/cntrlP01OL1805_1.dbf_20020<\/p>\n 916<\/p>\n mv \/ol0_oras02\/ORACLE\/P01OL1\/ctl\/cntrlP01OL1805_2.dbf \/ol0_oras02\/ORACLE\/P01OL1\/ctl\/cntrlP01OL1805_2.dbf_20020<\/p>\n 916<\/p>\n @New_controlfile.sql \u2013 control file\uc744 \uc7ac\uc0dd\uc131\ud558\ub294 \ubd80\ubd84. alter database open;<\/p>\n alter system switch logfile;<\/p>\n archive log list<\/p>\n alter database backup controlfile to trace ;<\/p>\n alter database backup controlfile to ‘\/ol0_orah01\/oracle\/adm\/P01OL1\/udump\/CTRL20020916_After’ ;<\/p>\n \uc704\uc640 \uac19\uc740 \uc21c\uc11c\ub85c \uc791\uc5c5\uc744 \ud558\uac8c \ub418\ub294\ub370.. \uc774\ub54c control file \uc744 create \ud558\ub294 \ubc29\ubc95<\/p>\n This section provides step-by-step instructions for creating new control files. If you followed the recommendations for database backups, you should already have a list of datafiles and online redo log files that reflect the current structure of the database. 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<\/a> 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 with normal priority, if possible. Use the IMMEDIATE or ABORT options only as a last resort. When creating the new control file, select the RESETLOGS option if you have lost any online redo log groups in addition to the control files. In this case, you will need to recover from the loss of the redo logs (Step 8<\/a>). You must also specify the RESETLOGS option if you have renamed the database. Otherwise, select the NORESETLOGS option. Edit the initialization parameter file of the database to indicate all of the control files created in Step 5<\/a> and Step 6<\/a> (not including the backup control file) in the CONTROL_FILES parameter. If you are renaming the database, edit the DB_NAME parameter to specify the new name. If you are creating the control file as part of recovery, recover the database. If the new control file was created using the NORESETLOGS option (Step 5<\/a>), you can recover the database with complete, closed database recovery. If the new control file was created using the RESETLOGS option, you must specify USING BACKUP CONTROL FILE. If you have lost online or archived redo logs or datafiles, use the procedures for recovering those files.
\n<\/span><\/p>\n
\n<\/span><\/p>\n\n
Creating New Control Files<\/span><\/h3>\n
\n<\/span><\/p>\nTo Create New Control Files<\/span><\/h5>\n
\n
\n<\/span><\/p>\n
\n<\/span><\/li>\n
\n<\/span><\/div>\n
\n<\/span><\/li>\n
\n<\/span><\/div>\n<\/li>\n
\n<\/span><\/li>\n
\n<\/span><\/li>\n
\n<\/span><\/p>\n
\n<\/span><\/li>\n