A detailed tutorial on the recovery of Oracle databases

Racle is pretty much the same, but the security and stability of Oracle's design is very good. So the corresponding configuration file will be more.

1, the original Oracle installation directory and the data directory to make a backup. Then install Oracle, and the installation path will be the same as the original. Install the "Software only" option, do not choose to install the database. For example: installed in the e:oracleproduct10.2.0 directory, you will find that there is only one db_1 directory in the directory.

2, then the Db_1networkadmin directory of Tnsnames.ora, Sqlnet.ora, Listener.ora files to the corresponding directory.
3. Configure Listener and TNS:

Run Lsnrctl start, you can create a listening service;

Use Net Manager to configure TNS, but do not test (the database is not up for sure the test is not passed);

Note: Configure TNS This can be omitted, because all the files after overwriting, and then through Net Manager will be found in the manager, but the machine hostname must be consistent, if not consistent, file coverage, you can modify here.

4, the original e:oracleproduct10.2.0 directory in the Oradata, Flash_recovery_area and admin directories are copied to the newly installed directory.

Note: Admin directory can only copy/admin/$SID/pfile folder, several other adump, Bdump, Cdump, Dpdump, Udump can create a new folder directly on the line.

5. Rebuilding Instance Service:

Oradim-new-sid Orcl-startmode Auto

Where ORCL is the name of the SID. If you have more than one library, you must run multiple times. (The rear-startmode auto can also not)

6, Reconstruction password file (This step can also be omitted, using the original password Pwdorcl.ora.) If the instance name is something else, replace the ORCL with another one:

Orapwd file= Path PASSWORD=ORCL entries=5

7, to the Serveices.msc to restart all Oracle-related instance services and monitoring. You can also restart the command line.

8, finally can pass

Sqlplus/nolog

Conn AS/SYSDBA;

Check to see if the database is restored. If not, check the report for any errors. What files are missing, then find the appropriate files, and put them in the new installation location. If you find that no corresponding error, see if the database is not started, you can connect, startup manually open the database.

As shown above, there is a lack of db_1 under the database and DBS directory of related documents.

When the above steps are completed, the database should be almost complete and restored. Recovery is primarily dependent on the following files:

A, initialization parameter file Init.ora
b, all data files. dbf
C, redo log files (online log, archive log) redo
D, Control documents
E, internal password file