I have a Oracle 11g R1 Standard Edition database on production server working on Windows 2008 R2 SE. Unfortunately server it not working properly (os/hardware failure) and I need to move it to temporary machine for a few days.

My first idea was to create full backup on production server and restore it on temporary. Second was, to duplicate database using RMAN. Both methods works fine, but it takes around 4 hours to complete all operations. Database should go back to production sever in few days, so again system will be stopped. It gives 8 hours of system unavailability.

Datafiles are around 60 GB and database is running in archivelog mode

Can you suggest me how can I minimize this time without violating Oracle SE license?

Thanks in advance

  • How big is the db? Running in archive log mode?
    – Brian McGinity
    Commented Jun 23, 2014 at 15:04
  • Hi Brian, its around 60 GB and is running in archivelog mode.
    – Norbert
    Commented Jun 23, 2014 at 15:11
  • By "without violating Oracle SE license" do you mean "only having one database mounted at a time"? Commented Jun 24, 2014 at 13:20

1 Answer 1


As a side note, rman is very fast when backing up to solid state disks. If you can get your hands on some put them in a raid you'll probably back up and restore in probably less than 30 minutes.

In either event, here's how to move the db to another host with hardly any downtime. Here's the overview:

1. do a full rman backup.

2. copy everything in the flash recovery area to the new host

3. go through the process of restoring the db to the new host.
   a. There are a handful of steps to do this.  It's not too hard.
   b. First the full backup is restored.
   c. Then each archive log is applied to the new instance.
   d. When all of the archive logs are have been applied, the db is opened.

Keep the production db up and running while you are doing steps 1,2,3a,3b. This may take a few hours if you have slow disks/network.

Once the level 0 backup is restored, apply the archive logs sitting in the flash recovery area which you copied in step 2.

At this point, all you need to do put the production db in read only mode and then copy and apply the last set of archive logs which were created after you copied the FRA. This should be very fast.

Then open the db and change clients so they now use the new db.

  • Thanks very much Brian, This is what I needed, but couldn't find anywhere how to do it. Just one more question: What do you mean by Apply in "apply the archive logs sitting in the flash recovery area which you copied in step 2" and "apply the last set of archive logs" ?
    – Norbert
    Commented Jun 23, 2014 at 19:10
  • Copy the FRA to the new server, this copies your L0 backup and the archive logs. Then restore the L0 backup and apply the archive logs. So this may take a few hours and the production server has produced more archive logs. Get these new archive logs and copy them to the new server. Then you'll apply these archive logs. Research rman's "recover until cancel" command.
    – Brian McGinity
    Commented Jun 23, 2014 at 23:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.