Re: Standby database as a reporting database ?

From: Paul Brewer <paul_at_paul.brewers.org.uk>
Date: Tue, 2 Oct 2001 21:52:08 +0100
Message-ID: <3bba2d5e_3@mk-nntp-1.news.uk.worldonline.com>

I agree with everything that's been said. Reminder, though:

A Read Only database is *exactly* what it says on the box. You cannot recompile any invalid objects. Nor can you write to a conventional TEMP tablespace .. you have to make it locally managed. You cannot submit *anything* which would generate redo.
Also, you have to be extremely careful not to do any unrecoverable actions on the master.
All in all, if at all practicable, I'd recommend keeping the standby database as a true standby for DR, and maintaining instance No. 3 if you want a separate reporting or MIS database.

Just my USD 0.02.

Paul

"Christian Svensson" <chse30_at_hotmail.com> wrote in message news:ccc2a7eb.0109280523.1515cfde_at_posting.google.com...
> Greetings !
>
> I am studying for the Backup & Recovery certification (Oracle 8i) and
> wonder if there are any means to make a standby database as a
> reporting database.
>
> What I have read so far is that if you open the standby db, it gets
> out of sync from the production db and will not apply the archived
> redo logs anymore.
>
> I cant be the only person thinking this is a waste of resources. There
> must be some ways to accomplish this. How is it in Oracle 9i ?
>
> Thanks for any ideas.
>
> /Christian Svensson
Received on Tue Oct 02 2001 - 15:52:08 CDT