Of course there is nothing special about restoring a database from the cloud on your own down-on-earth server, but it helps making this post cool and cloudy.
rman
Recently during restore of a large database (over 10 TB) we monitored the alert log looking for messages like «Full restore complete of datafile 42 to datafile copy … Elapsed time: 0:39:32»
After you have validated database as shown in previous post any corrupt database blocks will be reported in the view V$DATABASE_BLOCK_CORRUPTION. Now you want to find out the tables that used to have data in these blocks; those data have typically been lost if you have no backup of them or do not posses special tools like DUDE.
I worked with corrupt blocks in a database a few weeks ago and decided to write three posts about it so I don’t have to rethink all of it next time it happens. Hardware and the database have improved a lot, because I rarely run into this problem.
You may get error ORA-32012 if you are on 11g, but have the compatible parameter set to pre-11g in the database you are cloning from, and the spfile for the source database is stored in ASM when you do an RMAN duplicate from active database.
Using the CONVERT command in RMAN can be an efficient way to migrate a database from one OS to another, if they have the same endian.