Re: Managed recovery not working on Standby Database.

From: trub3101 <trub3101_at_sky.com>
Date: Thu, 3 Dec 2009 07:31:11 -0800 (PST)
Message-ID: <81c40f25-d134-4a93-9e89-2cf60cd53206_at_v25g2000yqk.googlegroups.com>

On 2 Dec, 22:59, joel garry <joel-ga..._at_home.com> wrote:
> On Dec 2, 12:45 pm, trub3101 <trub3..._at_sky.com> wrote:
>
>
>
>
>
> > Hi all,
>
> > Oracle Database 10g Enterprise Edition 10.2.0.3.0 Platform Windows
> > Server 2003
>
> > I am at a loss as to why managed recovery is not working on my standby
> > database as expected. All the archivelogs have transported
> > successfully across from the primary database to the standby database
> > but no recovery occurs on the standby.
>
> > Below are the details I have managed to gather so far. Of particular
> > interest is the value of 'RECOVERY_MODE' which is 'IDLE' even though I
> > started the standby correctly numerous times i.e.
>
> > shutdown immediate;
> > startup nomount;
> > alter database mount standby database;
> > alter database recover automatic managed standby database disconnect;
>
> > Anyway, this is what I have gathered so far:
>
> > SQL> archive log list
> > Database log mode              Archive Mode
> > Automatic archival             Enabled
> > Archive destination            USE_DB_RECOVERY_FILE_DEST
> > Oldest online log sequence     627
> > Next log sequence to archive   0
> > Current log sequence           629
> > SQL> l
> >   1  select     ds.dest_id id
> >   2  ,  ad.status
> >   3  ,  ds.database_mode db_mode
> >   4  ,  ad.archiver type
> >   5  ,  ds.recovery_mode
> >   6  --,        ds.protection_mode
> >   7  ,  ds.standby_logfile_count "SRLs"
> >   8  ,  ds.standby_logfile_active active
> >   9  ,  ds.archived_seq#
> >  10  from       v$archive_dest_status   ds
> >  11  ,  v$archive_dest          ad
> >  12  where      ds.dest_id = ad.dest_id
> >  13  and        ad.status != 'INACTIVE'
> >  14  order by
> >  15*    ds.dest_id
> > SQL> /
>
> >  ID STATUS    DB_MODE         TYPE RECOVERY_MODE    SRLs ACTIVE
> > ARCHIVED_SEQ#
> > --- --------- --------------- ---- ---------------- ---- ------
> > ---------------
> >   2 VALID     MOUNTED-STANDBY ARCH IDLE                0
> > 0
> > 0
> >  10 VALID     MOUNTED-STANDBY ARCH IDLE                0
> > 0
> > 0
> >  11 VALID     MOUNTED-STANDBY ARCH IDLE                0
> > 0
> > 628
>
> > SQL> select * from
> >   2  (select max(sequence#) as "Last Archived" from v$log_history),
> >   3  (select max(sequence#) as "Last Applied" from v$archived_log
> > where applied='YES');
>
> >   Last         Last Applied
> > Archived
> > ---------------
> > ---------------
> >           148           148
>
> > Thanks in advance for any suggestions,
> > tb3101
>
> What does your alert log say about those alter database commands?
>
> What are the values of
> STANDBY_FILE_MANAGEMENT
> STANDBY_ARCHIVE_DEST
> FAL_SERVER
> FAL_CLIENT
>
> Do you have srl's?  Which DG options are you intending on using? ASM?
>
> jg
> --
> _at_home.com is bogus.http://www.signonsandiego.com/news/2009/nov/30/hm-recollected-famous-...- Hide quoted text -
>
> - Show quoted text -

Hi Joel,

Thanks for your reply.

I am not using DG per se just running standby sql here and there.

Here are the values for those parameters you asked about.

SQL> show parameter FAL

NAME                                 TYPE        VALUE
------------------------------------ -----------
-----------------------------------
fal_client                           string      LIVE_PRIMARY
fal_server                           string      LIVE_STANDBY

SQL> show parameter standby_file_management

NAME                                 TYPE        VALUE
------------------------------------ -----------
-----------------------------------
standby_file_management              string      AUTO

SQL> show parameter standby_archive_dest

NAME                                 TYPE        VALUE
------------------------------------ -----------
-----------------------------------
standby_archive_dest                 string

location=USE_DB_RECOVERY_FILE_DEST

1* select standby_logfile_count from v$archive_dest_status

STANDBY_LOGFILE_COUNT

---

                    0
                    0
                    0
                    0
                    0
                    0
                    0
                    0
                    0
                    0
                    0

11 rows selected.

Thanks again for your assistance with this matter.

tb3101 Received on Thu Dec 03 2009 - 09:31:11 CST