System corruption: Port Oracle (9.2.0.1) database (no backup data files for recovery)

System Environment of machine:

Software: windows2003server, oracle9.2.0.1
Hardware: dellsc420 (p43.0, 2 GB memory, 160gsata hard drive)

Oracle data volume: 11 GB.

Symptoms: the LAN is infected with viruses, the network is paralyzed, and the system is damaged.

Solution:
1. Remove the server hard disk and mount it to the Dell dimension 4550 server to retrieve the Oracle data (data file, control file, redo file, archive logfile, spfile, pwdfile. Since the redo file cannot be retrieved, the undotbs tablespace file can only be rebuilt after it is restored ).

2. Install oracle on host B according to the Oracle environment configuration of host.

3. Shut down all services on machine B, and overwrite the data file, control file, redo file, archive logfile, spfile, and pwdfile files on machine B.
Note: Data File, control file, redo file, archive logfile, spfile, pwdfile file File Location: If your Oracle system and system tablespace are installed together. This is very easy to find. For example, my oraclehome is on disk D, and the SID is: "ogtlogdb"

Pwdfile, spfile, etc. in: D: \ oracle \ admin \ ogtlogdb
Datafile, redofile, etc. in: D: \ oracle \ oradata \ ogtlogdb

4. log on to "sys/sys @ ogtlogdb as sysdba" in sqlplus. (when I first used SQL, it was unsuccessful under cmd, therefore, input "sqlplus" in the command line and then "sys/sys @ ogtlogdb as sysdba ").

5. Shut down the database: SQL> Shutdown

6. Restart the database and remember to load the file with errors during startup: SQL> startup force
The screen is as follows:
Total system global area 126950220 bytes
Fixed size 453452 bytes
Variable Size 109051904 bytes
Database buffers 16777216 bytes
Redo buffers 667648 bytes
The database has been loaded.
ORA-01157: unable to identify/lock data file 9-see dbwr trace file
ORA-01110: data file 9: 'd: \ oracle \ oradata \ xinahe \ users01.dbf'

7. Put all errors and lost files offline drop
SQL> alter database datafile 'd: \ oracle \ oradata \ orcl \ undotbs01.dbf' offline drop;
If another data file error occurs here, run the preceding statement to drop the offline data file.

8. SQL> alter database open;
Screen return: database altered;
If any data file prompts an error, perform Step 5 repeatedly.
Until you execute this step, the screen Returns database altered.

9. Recreate the undotbs tablespace: Create undo tablespace undotbs datafile 'C: \ oracle \ oradata \ orcl \ undotbs02.dbf' size 100 m;
Screen return: tablespace created.

10. Fixed the data file with errors in step 5.
SQL> recover automatic datafile 1;
Screen return: Media recovery is completed.
SQL> recover automatic datafile 19;
Screen return: Media recovery is completed.
Use the preceding statement to restore all offline drop data files.

11. Put the offline drop file online again:
SQL> alter database datafile 'd: \ oracle \ oradata \ orcl \ undotbs01.dbf 'online;
SQL> alter database datafile 'd: \ oracle \ oradata \ orcl \ undotbs019.dbf 'online;

12. Alter database open;
Screen return: database opened.

13. Restart the machine (set Oracle service to auto start ).

Note: If the system01.dbf file is damaged after an oracle power failure occurs, you can use the above methods to restore the table. If the table is actually restored or the archive mode is not used, you can use:
Implicit commands of the Oracle System:
Alter system set "_ allow_resetlogs_upload uption" = true scope = spfile;

Change the UNDO log to manual mode:
Alter system set undo_management = 'manual' scope = spfile;

 

A few minutes later, shutdown and start again to temporarily read data.