Delete the control file of the Oracle database instance by mistake

Mistaken DeletionOracle DataThe control file of the database instance will bring a lot of trouble to the operations of the Oracle database. The following will give you a detailed explanation and hope to help you.

When I backed up data two days ago, I found that the size of the C: \ oracle \ product \ 10.2.0 \ oradata \ GXSN \ TEMP01.DBF file was much larger than 23G, completely consuming the C drive space, in a rush, I thought that the file in the oradata/GXSN folder was a temporary file and deleted completely.

Because Oracle data files are stored in the E disk, it is unknown that oradata/GXSN stores control files, which makes the database unusable. I tried to recreate the control file by querying relevant information, but found that the reconstruction control file was backed up on the premise that the ORACLE control file has been backed up. I have not backed up the control file of Oracle before, therefore, it cannot be recovered.

Throughout the process of solving the problem, I tried a variety of ideas. Although it failed, it exercised its ability to solve the problem and summed up some experience.

0. for help with Oracle China technical support, it seems that there is no human service on weekends and it will take workdays. Failed)

1. Use EasyRecovery to restore the deleted control file. Because the elastic disk on the server is large and reaches 3 TB, EasyRecovery cannot be used. If other data recovery software is used, deleted data cannot be recovered. Failed)

2. query related information and try to recreate the control file. Failed)

Create controlfile reuse set DATABASE orcl RESETLOGS noARCHIVELOG

MAXLOGFILES 32

MAXLOGMEMBERS 3

MAXDATAFILES 32

MAXINSTANCES 16

# MAXLOGHISTORY 1600

LOGFILE

Group 1 ('e: \ oracle \ product \ 10.2.0 \ oradata \ orcl \ redo01.log') size 100 k,

Group 2 ('e: \ oracle \ product \ 10.2.0 \ oradata \ orcl \ redo02.log ') size 100 k,

Group 3 ('e: \ oracle \ product \ 10.2.0 \ oradata \ orcl \ redo03.log ') size 100 k,

Datafile

'E: \ oracle \ product \ 10.2.0 \ oradata \ orcl \ users01.dbf ',

'E: \ oracle \ product \ 10.2.0 \ oradata \ orcl \ undotbs01.dbf ',

'E: \ oracle \ product \ 10.2.0 \ oradata \ orcl \ system01.dbf ',

'E: \ oracle \ product \ 10.2.0 \ oradata \ orcl \ sysaux01.dbf ',

'E: \ oracle \ product \ 10.2.0 \ oradata \ orcl \ example01.dbf ';

3. Create the same GXSN database on another machine and import the control file to the database on the server.

4. Create an ORACLE service instance on the server, generate the corresponding control file, and import the control file to the database GXSN, but an error is found.

5. Delete the new database instance. The original database cannot be connected using SQLPLUS on the CMD console.

Sqlplus/nolog

Conn/as sysdba

Error With ORA-12360: TNS: protocol adapter

The database cannot be connected to the original database instance.

Two or three TBS of data can only be reinput. This mistake is really a huge loss! In the future, you must calm down and be impatient. You need to take a deeper step in ORACLE learning to avoid making such a low-level and serious mistake!