Go Back   Rhinocerus > Newsgroup > Newsgroup comp.databases.oracle.server

Reply
 
Thread Tools Display Modes
  #1 (permalink)  
Old 10-28-2009, 02:57 PM
wagen wheels
Guest
 
Posts: n/a
Default archived redo logs and standby db

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

Reply With Quote
Alt Today
Advertising
 
and become member of Rhinocerus
Standard Sponsored Links

  #2 (permalink)  
Old 10-28-2009, 03:39 PM
Steve Howard
Guest
 
Posts: n/a
Default Re: archived redo logs and standby db

On Oct 28, 11:57*am, wagen wheels <wagen...@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
Reply With Quote
  #3 (permalink)  
Old 11-05-2009, 08:08 PM
wagen wheels
Guest
 
Posts: n/a
Default Re: archived redo logs and standby db

Thanks Steve.

Reg 2 - I have the db in managed recovery (did not open in READ ONLY)
with no logins and i still see SWITCHOVER_STATUS showing "NOT
ALLOWED".

Is there a way in oracle (10g/11g) where oracle can automatically
delete the standby archived redo log if it is successfully applied.
Trying not to write a script if there is something built in. I checked
the docs/web didn't find anything so far.

Thanks for any pointers/help.
Reply With Quote
 
Reply

Popular Tags in the Forum
archived, logs, redo, standby

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off




All times are GMT. The time now is 02:20 AM.


Copyright ©2009

LinkBacks Enabled by vBSEO 3.3.0 RC2 © 2009, Crawlability, Inc.