Re: Problem with 9.0.1.3 RMAN CONFIGURE Command

There is a resync done *after* every backup.

What makes you say that a backup doesn't resynch "correctly"?

Regards
HJR "Klaus Naumann" <spock_at_mgnet.de> wrote in message news:s66eaa.5k3.ln_at_192.168.1.1...
> On Fri, 26 Apr 2002 23:54:14 +0200, Howard J. Rogers wrote:
>
> Hello Howard,
>
> > You're running with a recovery catalog. The command you issued gets
> > stored in the controlfile of the target database. When you resync the
> > catalog, you should see the new setting picked up (and remember that a
> > resync occurs everytime you perform a backup, copy or a
> > restore/recovery).
>
> this seems to be the problem. I now did a manual
> resync (resync catalog;) and the changed value was accepted.
> But the DB did a backup this night. So doing a
> backup doesn't resync the catalog correctly, it
> seems. Might this be a bug ?
>
> Thanks for the help of course !
>
> Thanks in advance, Klaus
>
>
> >
> > Were you running without a catalog, the command would be picked up
> > immediately.
> >
> > Regards
> > HJR
> >
> >
> > "Klaus Naumann" <knaumann_at_gmx-ag.de> wrote in message
> > news:3P8y8.7$Wz1.5985_at_news.ecrc.de...
> >> Hi all,
> >>
> >> I'm seeing some trouble with RMAN on a 9.0.1.3 DB on a SUN E250
> >> (Solaris 2.6). I'll explain it by example:
> >>
> >> First, connect to catalog and to database:
> >>
> >> rman target / catalog rman9/***********@rcvcat
> >>
> >> This works fine:
> >>
> >> Recovery Manager: Release 9.0.1.3.0 - Production
> >>
> >> (c) Copyright 2001 Oracle Corporation. All rights reserved.
> >>
> >> connected to target database: EDB01 (DBID=2336558208) connected to
> >> recovery catalog database
> >>
> >> RMAN>
> >>
> >> Let's look at the stored parameters:
> >>
> >> RMAN> show all;
> >>
> >> RMAN configuration parameters are:
> >> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
> >>
> >> and so on ....
> >>
> >> Now I want to change a stored parameter:
> >>
> >> RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
> >>
> >> old RMAN configuration parameters:
> >> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS; new RMAN
> >> configuration parameters:
> >> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS; new RMAN
> >> configuration parameters are successfully stored
> >>
> >> ok, looks good also. But now we're at the problem point. Looking at the
> >> parameters again, I can see that it's _not_ changed:
> >>
> >> RMAN> show all;
> >>
> >> RMAN configuration parameters are:
> >> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
> >>
> >> Am I missing something or is this a bug ?
> >>
> >> Thanks, Klaus
> >>
> >> --
> >> Klaus Naumann
> >> Database Administration
> >> GMX Aktiengesellschaft
> >> Riesstrasse 17, 80992 München
> >> Telefon +49.89.143 39-0
> >> Telefax +49.89.143 39-100
> >> mailto:knaumann_at_gmx-ag.de
> >> http://www.gmx.net/
>
> --
> Full Name : Klaus Naumann | (http://www.mgnet.de/) (Germany)
> Nickname : Spock | Org.: Mad Guys Network
> Phone / FAX : ++49/177/7862964 | E-Mail: (spock_at_mgnet.de)
> PGP Key : www.mgnet.de/keys/key_spock.txt
Received on Sat Apr 27 2002 - 12:06:35 CDT