Re: RMAN recovery incomplete issue while recovering in DG

  • From: "Shastry(DBA)" <shastry17@xxxxxxxxx>
  • To: ora-apps-dba@xxxxxxxxxxxxx, Steve Kirby <kirby@xxxxxxxxxxxxxxxxxxx>
  • Date: Sat, 5 Mar 2011 14:14:19 +0530

Hi Steve/Harel,

Thanks for your responses so far. The issue got resolved and used
filesperset as an option while taking backup and recovery went fine..
Appreciate your help very much.

Regards,
Ananth

On Wed, Mar 2, 2011 at 11:33 PM, Steve Kirby <kirby@xxxxxxxxxxxxxxxxxxx>wrote:

>  I suspect I am missing something, but lets go though some ideas.
>
> 1) Recreate the standby instance outside of RMAN since RMAN is giving you
> problems
>          - this ensures that you have a current copy and will address you
> concerns about SCN numbers.
>         - If you have time you can even test a failover
> 2) Are there other scripts running that might be getting in the way of the
> RMAN backup?  e.g. another backup or some other process?
> 3) You are not using the same RMAN command as I would be using ... but I
> don't have a 9.2 instance to test on.  I was using 'dgmgrl' at that time.
>         See Metalink note: 180031.1 and 201669.1
> 4) Why remain on 9.2?  Dataguard has vastly improved, as has RMAN, since
> 9.2.
> 5) Because so much is going on, and I don't know the load, you might look
> at Metalink Note: 841765.1 for why you are seeing the 'noredo' behavior that
> you are seeing.
>         - Forcing a logfile switch and then backup might update the SCN's
> ...
>
> I am afraid I will be traveling for most of today or I would jump in a bit
> more.
>
> Steve
>
>
>  ------------------------------
> *From:* ora-apps-dba-bounce@xxxxxxxxxxxxx [mailto:
> ora-apps-dba-bounce@xxxxxxxxxxxxx] *On Behalf Of *Shastry(DBA)
> *Sent:* Wednesday, March 02, 2011 9:28 AM
> *To:* oracle-l; ora-apps-dba@xxxxxxxxxxxxx
> *Subject:* RMAN recovery incomplete issue while recovering in DG
>
>  Hi All,
>
> We are having the issue with dataguard lag issue from production due to
> heavy generation of archives and had a challenge to keep in synch of DG with
> production database. We later tried to use the manual recovery option to see
> if we can make the recovery faster rather than script which ships the
> archive and then get applied, but it did not help. Finally we tried with
> RMAN option like creating a catalog database and registering the DG as
> level0 (since its 9.2.0.8 version) and taking level 1 at production side and
> later have the backup piece in DG host to apply RMAN with "recover database
> no redo".
> We are facing challenge in this where RMAN did not errored out in any
> stage/phase but only few datafiles got updated with the latest SCN and rest
> were left untouched by RMAN.
> Also if the Oracle is on 10g we just need a level1 backup and apply the
> changes in DG database without any level0 catalog.
>
> What we observed was, there were 27 total backup pieces were generated in
> level1 backup, but first 10 backup pieces were not cataloged and looks
> missing (wierd).
>
>  1.     The recovery noredo has not applied any changes to the files which
> are dated 22-FEB and few 28-FEB.
>
> 1.     When you start recovery in manual mode, it asks for archive files
> generated on Feb22
>
>
>  1.     The backupsets which are not listed in RMAN catalog but exists in
> physical media is of *Size 0* in the rman catalog.  *The first 10
> backupsets are kicked out*. But the backup piece is in available status
> and the files returns no rows.
>
>
>
> RMAN> *list backupset 198935;*
>
>
>
> List of Backup Sets
>
> ===================
>
>
>
> BS Key  Type LV Size       Device Type Elapsed Time Completion Time
>
> ------- ---- -- ---------- ----------- ------------ ---------------
>
> 198935  Incr 1  0          DISK        00:50:01     01-MAR-11
>
>         BP Key: 198569   Status: AVAILABLE   Tag: SCPSTBY
>         Piece Name: /oracle/product/9.2.0.8/rman/2pn63c7m
>
>
>  RMAN> *list backup of datafile "/dev/vgssoprd7/rv4000-63";*
>
> returns No rows.
>
>
>
>  Looks like  some threshold value of control is getting hit and the first
> files/backupsets are kicked out when new files/backupsets are generated.
>
>
>
> 1.     Checked if it’s the file size which is causing issue but it is not
> as other big files were taken and applied.
>
>
>  Need your help in showing some ideas and light on the same as its 9i
> version and having challenges.
>
> Database version : 9.2.0.8
> Platform              : HP-UX
>
> Thanks,
> Ananth
>

Other related posts: