Re: archived redo logs and standby db

From: Steve Howard <stevedhoward_at_gmail.com>
Date: Wed, 28 Oct 2009 09:39:07 -0700 (PDT)
Message-ID: <78eba325-a8af-4c4c-9f69-69ac2ca1b36b_at_k17g2000yqh.googlegroups.com>

On Oct 28, 11:57 am, wagen wheels <wagen..._at_yahoo.com> wrote:
> Hi,
>
> Oracle11g 11.1.0
> Linux (RHEL AS 4.4)
>
> - Primary and standby db (physical standby with standby redo logs)
> - Standby db in read only mode (haven't setup real time apply yet)
> - Primary: log_archive_dest_2 = LGWR ASYNC
>
> I have two questions
>
> 1) We have a need to delete the archived redo logs on the standby
> database AFTER it's applied. I plan to use the following query, get
> the seqence number and then use RMAN to delete the APPLIED archived
> redo logs that are on disk.
> select max(sequence#) max_applied_seq from gv$archived_log where
> applied='YES';
>
> 2) I have setup the standby db as per oracle documentation, logs are
> being applied and the standby db is in sync with the primary. When I
> execute the query SELECT SWITCHOVER_STATUS FROM gv$database ; on the
> STANDBY DB it shows
>
> SWITCHOVER_STATUS
> --------------------
> NOT ALLOWED
>
> NOTE: we have read only users connected to the standby db
>
> Why is the switchover_status showing "NOT ALLOWED"?
> What are the things i should check?
>
> Thanks for your help.
> wagen

Hi Wagen,

1 - This is how we do it. The only thing I would mention is if the standby is a cluster you will also have to filter on thread. 2 - You cannot have any logins on the standby database to switchover. You can do a "with session shutdown" clause to disconnect them.

HTH, Steve Received on Wed Oct 28 2009 - 11:39:07 CDT