1. Go into Server Manager and connect internal.
2. If the database is not already down, shut it down (normal or immediate).
3. Mount the database.
STARTUP MOUNT
4. Generate a backup trace of the control file.
ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
This statement will generate a new trace file in the user_dump_dest directory. To find out where that directory is, simply type
SHOW PARAMETER USER.
Once in that directory, search by timestamp for a newly created user trace file with extension "trc".
5. Shut down the database (normal or immediate).
6. Take a full backup of the database (including all data files, redo log files, and control file, if any).
7. If there is any copy of the current control file out there in the operating system, remove it now.
8. Edit the new trace file to convert it into a SQL script. If properly edited, the new trace file becomes an executable SQL script, the execution of which will create a new control file.
8.1 Remove the header of the file.
Delete from the first line of the file, which should read "Dump file <trace file name>", through the line immediately preceding the STARTUP NOMOUNT statement, which should read "# only if the current version of all online logs are available," so that the first line of the file now contains STARTUP NOMOUNT.
8.2 Make any other necessary changes to the file.
If you are recreating the control file to bump up hardcoded database parameters such as MAXDATAFILES or MAXINSTANCES, replace the current values with new ones.
9. In the same directory where the trace file is, go into Server Manager and connect internal.
10. Run the edited trace file as if it were a SQL script.
For example, if the trace file is called ora_7489.trc, you should enter @ora_7489.trc At this point, if you get the message "Statement processed," the database should be open with a brand new control file.
You should shut the database down (normal or immediate) next, and take a full backup. ●龙飞虎○
2. If the database is not already down, shut it down (normal or immediate).
3. Mount the database.
STARTUP MOUNT
4. Generate a backup trace of the control file.
ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
This statement will generate a new trace file in the user_dump_dest directory. To find out where that directory is, simply type
SHOW PARAMETER USER.
Once in that directory, search by timestamp for a newly created user trace file with extension "trc".
5. Shut down the database (normal or immediate).
6. Take a full backup of the database (including all data files, redo log files, and control file, if any).
7. If there is any copy of the current control file out there in the operating system, remove it now.
8. Edit the new trace file to convert it into a SQL script. If properly edited, the new trace file becomes an executable SQL script, the execution of which will create a new control file.
8.1 Remove the header of the file.
Delete from the first line of the file, which should read "Dump file <trace file name>", through the line immediately preceding the STARTUP NOMOUNT statement, which should read "# only if the current version of all online logs are available," so that the first line of the file now contains STARTUP NOMOUNT.
8.2 Make any other necessary changes to the file.
If you are recreating the control file to bump up hardcoded database parameters such as MAXDATAFILES or MAXINSTANCES, replace the current values with new ones.
9. In the same directory where the trace file is, go into Server Manager and connect internal.
10. Run the edited trace file as if it were a SQL script.
For example, if the trace file is called ora_7489.trc, you should enter @ora_7489.trc At this point, if you get the message "Statement processed," the database should be open with a brand new control file.
You should shut the database down (normal or immediate) next, and take a full backup. ●龙飞虎○
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货