Re: Standy DB, Replication

Been there, done that...

We had the same requirements a while back on Oracle 7.3 and finally settled on an archivelogs strategy. Starting with a mirror image of the production DB on a report DB (different machine but identically configured), we applied archivelogs to the report DB every night at midnight (which took about 1 hour). Reports were being done on the report DB with data of the previous day. Don't know if this is acceptable for your report DB.

Regards,

Marc Mazerolle

Joo Wah wrote:

> Hi,
>
> We are required to setup an estimated 2 tera byte Db for an online
> transaction processing project.
> The db has to keep up a high level of service level. (24x7)
> Besides there is also large regular back-end processing jobs.
>
> The problem is that there are also requirements to do a substantial amount
> of reporting from the data on this database.
> Possibly some large backend and also user reports.
>
> My peers are suggesting we do replication on the database to a seperate
> machine for the reporting.
> My feeling is that doing replication on 2 tera of data is quite unthinkable
> and I have no experience on
> what the performance impact on the db wiil be like. (It could be better off
> to let reportingbe done on the db itself).
> (We are talking about possibly 3hrs snapshots).
>
> I was also thinking of setting up a standby database instead and opening it
> as only read-only database.
> I have read somewhere that 8i can do that but the current version we are on
> is 8.0.5 so I'm not sure it can be archieved.
>
> Anyone has such setup or experience to share ?
> I'm open to any suggestions and comments
Received on Wed Jul 07 1999 - 14:30:01 CDT