Restore data from oradata for Oracle 11g on RedHat Linux

The mofei theorem verifies everything that exists, so the Oracle 11g installed on RedHat is hit. I was careful when installing the machine and did not dare to restart the machine (because it was my first installation, so I was particularly worried). I was afraid of problems, so I did not close the machine after the installation was successful. Just a few days ago, the power was cut off due to data center rectification. Restart all the machines. After this restart, the oracle I installed will be suspended. At that time, my heart became cold. There is more than 260 GB of data in it. I'm dizzy. For oracle cainiao like me, it was like a day crash. As a result, duniang is quickly opened and how to restore the search. After reading a circle, Select Restore from oradata. To ensure security, I copied all the data of more than 260 GB to the B server.

First, you need to use the original system disk to create A system on machine C according to the settings on machine A (the oracle-mounted machine. Make sure that the machine name and IP address are the same here. Then, use the same version of oracle installation disk to install Oracle on the C machine. During installation, you must set the environment variable (The. bash_profile file). The environment variable here must be consistent with that on machine. Open the console and log on to the oracle database with sys in sqlplus. Then, run the shutdown immediate command to close the oracle database.

Copy all oradata data on machine B to the oracle Installation Directory of machine C, and overwrite the oradata folder on machine C. To ensure security, you can use the chown-R oracle: oinstall/home/app/oradata and chown-R 775/home/app/oradata commands to set the file attributes. After that, do not rush to start the database. Instead, delete all files in flash_recovery_area. Create a folder with the same name as the SID (case-insensitive), and copy the control01.ctl file in the lower-level folder of the oradata folder to the folder with the same name as the SID created in the flash_recovery_area file, and rename it control02.ctl.

After completing these operations, you can use the startup command to open the database. If no error is reported, it can be used normally. (I passed the test on both machines)