Thanks for your answer Tony. You're right, I need to expand my question a bit so that people can visualise the situation clearer.
The application is made up of multiple databases - one is a single global database and the other databases(min. of 2), will occur for each region that cuts over to use the application. (We're not going big-bang.)
Data that is stored in the global database is a combination of common data and different data, from that stored in the regional databases. (Therefore, we're not able to use Oracle replication.)
The recovery strategy needs to solve how the application can recover itself if one of the databases, for example, becomes corrupt.
We need to have a solution that makes each of the databases consistent with each other i.e. up to a specific transaction.
The technical team are looking at reducing the risk by adding mirroring on the global layer, in the aim to reduce data loss. However, we still have to build an application recovery solution.
The solution that I'm looking at is building reconciliation reports and programs that will recreate the data from the Global database.(If data isn't present in the global database that is required in the regional database, then I'm looking at defaulting this to dummy values.)
Do you have any thoughts on my proposal?
Thanks
Jenny