Re: RMAN Backup as Copy - Active Duplicate - Logfile Registered and has Known Backup

From: David Barbour <david.barbour1_at_gmail.com>
Date: Fri, 27 Mar 2015 14:53:48 -0500
Message-ID: <CAFH+ifeU8JkJF_r16cCSFZO3wbd-iEOSj3kLgQc=zb5PeyhK5g_at_mail.gmail.com>

Backup is there as well:

RMAN> list backup of ARCHIVELOG SEQUENCE 29639 THREAD 1;

List of Backup Sets

---

BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ ---------------

74769   5.11G      DISK        00:00:41     27-MAR-15
        BP Key: 74769   Status: AVAILABLE  Compressed: NO  Tag:
P00ARCHIVELOG
        Piece Name:

+P00FRA/p00/backupset/p00xxxxx_1469727213_875426311_s114680_p1_c1

  List of Archived Logs in backup set 74769   Thrd Seq Low SCN Low Time Next SCN Next Time

• ------- ---------- --------- ---------- --------- 1 29639 115540219707 27-MAR-15 115547247225 27-MAR-15

BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ ---------------

74787   5.64G      DISK        00:00:13     27-MAR-15
        BP Key: 74787   Status: AVAILABLE  Compressed: NO  Tag:
P00ARCHIVELOG
        Piece Name:

+P00FRA/p00/backupset/p00xxxxx_1469727213_875440811_s115685_p1_c1

  List of Archived Logs in backup set 74787   Thrd Seq Low SCN Low Time Next SCN Next Time

• ------- ---------- --------- ---------- --------- 1 29639 115540219707 27-MAR-15 115547247225 27-MAR-15

RMAN> On Fri, Mar 27, 2015 at 2:45 PM, David Barbour <david.barbour1_at_gmail.com> wrote:

> RMAN> LIST ARCHIVELOG SEQUENCE 29639 THREAD 1;
>
> using target database control file instead of recovery catalog
> List of Archived Log Copies for database with db_unique_name P00
> =====================================================================
>
> Key Thrd Seq S Low Time
> ------- ---- ------- - ---------
> 209672 1 29639 A 27-MAR-15
> Name:
> +P00ARCH01/p00/archivelog/2015_03_27/thread_1_seq_29639.509.875426153
>
> 209633 1 29639 A 27-MAR-15
> Name: +P00ARCH01/p00/saparch/1_29639_806417901.dbf
>
> 209598 1 29639 A 27-MAR-15
> Name: +P00ARCH02/p00/saparch/1_29639_806417901.dbf
>
>
> On Fri, Mar 27, 2015 at 2:27 PM, Seth Miller <sethmiller.sm_at_gmail.com>
> wrote:
>
>> David,
>>
>> Are you sure the archive log is registered with the production control
>> file?
>>
>> LIST ARCHIVELOG SEQUENCE 29639 THREAD 1;
>>
>> Seth Miller
>>
>> On Fri, Mar 27, 2015 at 12:46 PM, David Barbour <david.barbour1_at_gmail.com
>> > wrote:
>>
>>> Oracle 11gR2 on Linux 6.4 using ASM
>>>
>>> I'm missing something ......
>>>
>>> Performing an active duplicate of our production database. We changed
>>> the archive log destination on the test system to use the FRA rather than
>>> the specific duplexed archive log destinations on production.
>>>
>>> All the datafiles are copied, and MOST of the archivelogs. The
>>> duplicate log is reporting:
>>>
>>> channel ORA_AUX_DISK_1: starting archived log restore to default
>>> destination
>>> channel ORA_AUX_DISK_1: restoring archived log
>>> archived log thread=1 sequence=29639
>>> channel ORA_AUX_DISK_1: reading from backup piece
>>> +P00FRA/p00/backupset/p00xxxxx_1469727213_875440811_s115685_p1_c1
>>> channel ORA_AUX_DISK_1: ORA-19870: error while restoring backup piece
>>> +P00FRA/p00/backupset/p00xxxxx_1469727213_875440811_s115685_p1_c1
>>> ORA-19505: failed to identify file
>>> "+P00FRA/p00/backupset/p00xxxxx_1469727213_875440811_s115685_p1_c1"
>>> ORA-17503: ksfdopn:2 Failed to open file
>>> +P00FRA/p00/backupset/p00xxxxx_1469727213_875440811_s115685_p1_c1
>>> ORA-15001: diskgroup "P00FRA" does not exist or is not mounted
>>> ORA-15001: diskgroup "P00FRA" does not exist or is not mounte
>>> failover to previous backup
>>>
>>> During the duplicate process, a couple of archivelog bacups were made to
>>> disk on the production system to +P00FRA/p00/backupset/
>>>
>>> Those files are on the +P00FRA diskgroup.
>>>
>>> Additionally, the archivelogs the duplicate is looking to find have not
>>> been deleted from the archivelog destination. So I figured I'd just copy
>>> them over. But regardless of how I do it, I get a 'skipping backup' as
>>> follows:
>>>
>>> RMAN> backup as copy reuse archivelog like
>>> "+P00ARCH01/p00/archivelog/2015_03_27/thread_1_seq_29639.509.875426153"
>>> 2> auxiliary format "+S00FRA";
>>>
>>> Starting backup at 27-MAR-15 12:33:32
>>> using channel ORA_DISK_1
>>> skipping archived log of thread 1 with sequence 29639; already backed up
>>> Finished backup at 27-MAR-15 12:33:32
>>>
>>> I reset the parameter CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE
>>> DISK but still get the error.
>>>
>>> Any ideas?
>>>
>>
>>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Mar 27 2015 - 20:53:48 CET