Then you can perform the reconstruction of the bad control file and at some later time shut down and restart the database after editing the CONTROL_FILES initialization parameter to include the recovered control file. Remove the bad control file from CONTROL_FILES setting and you can restart the database immediately. In the Datafiles box, change the path to the new location. For each tablespace that you want to redirect: Expand the tablespace. To redirect individual tablespaces and datafiles, click Tablespaces and datafiles. If you have multiplexed control files, you can get the database started up quickly by editing the CONTROL_FILES initialization parameter. To redirect the database, click Database, and then enter the full path for the new location of the database. Start SQL*Plus and open the database: SQL> STARTUP With the instance shut down, use an operating system command to copy the current copy of the control file to a new, accessible location: % cp /u01/oracle/prod/control01.ctl /u04/oracle/prod/control03.ctlĮdit the CONTROL_FILES parameter in the initialization parameter file to replace the bad location with the new location: CONTROL_FILES = (/u01/oracle/prod/control01.ctl, This procedure assumes that one of the control files specified in the CONTROL_FILES parameter is inaccessible due to a permanent media failure and that you have a multiplexed copy of the control file. Recovering from Permanent Media Failure Using a Control File Copy
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |