This discussion is archived
6 Replies Latest reply: Dec 6, 2012 6:49 AM by Dird RSS

11g clone (mystical RMAN-05575: CONTROLFILE issue)

Dird Pro
Currently Being Moderated
Hi,

There seems to be no information really existing for RMAN-05575 (MOS has no knowledge on it). Took a backup & had issues yesterday, wondering if someone has had/solved this error before?
Full backup was done yesterday.
Datafiles: 02:10-09:12am
Archive logs: 10:10-12:20 (copied based on the log switch value...attempted to move 5 files before, 2 files over the specified switch value at around 9:30)
Control file: 12:20 (after the archive logs finished copying to new system)
rman auxiliary / <<EOF >> logger
run
{
DUPLICATE TARGET DATABASE TO CSTESTA UNTIL TIME "TO_DATE('20121205:09:13:10','YYYYMMDD:HH24:MI:SS')" -- set to slightly after archives go
BACKUP LOCATION '/nfs_orawork/BACKUP/CSPRODA1';
}

EOF
But this errors with the following:
connected to auxiliary database: CSTESTA (not mounted)
Starting Duplicate Db at 05-DEC-12
RMAN-03002: failure of Duplicate Db command at 12/05/2012 16:15:42
RMAN-05501: aborting duplication of target database
RMAN-05575: CONTROLFILE backup created before TO_DATE('20121205:09:13:00','YYYYMMDD:HH24:MI:SS') not found in /nfs_orawork/BACKUP/CSPRODA1
If I change the time of the to_date to after the control file timestamp it was backed up (say 12:30) it runs further but then it has lots of archive logs missing (to restore to that point in time). Anyone seen this issue before with 11g? I want to restore as far as the copied archivelogs allow me to, not the total number of logs mentioned in the control file.

Any help greatly appreciated :)
Mike
  • 1. Re: 11g clone (mystical RMAN-05575: CONTROLFILE issue)
    Shivananda Rao Guru
    Currently Being Moderated
    Hello,
    rman auxiliary / <<EOF >> logger
    run
    {
    DUPLICATE TARGET DATABASE TO CSTESTA UNTIL TIME "TO_DATE('20121205:09:13:10','YYYYMMDD:HH24:MI:SS')" -- set to slightly after archives go
    BACKUP LOCATION '/nfs_orawork/BACKUP/CSPRODA1';
    }
     
    EOF
    Please refer this http://shivanandarao.wordpress.com/2012/04/28/duplicating-database-without-connecting-to-target-database-or-catalog-database-in-oracle-11g/ to make sure that you have the steps run in the correct way.



    Regards,
    Shivananda
  • 2. Re: 11g clone (mystical RMAN-05575: CONTROLFILE issue)
    Dird Pro
    Currently Being Moderated
    Hi,

    Yes, same steps. I tried commenting out the UNTIL TIME part but it said: RMAN-05541: no archived logs found in target database

    Edit: Should there be a control file backup in the backup location? Wouldn't this point to file locations on prod?

    Mike

    Edited by: Dird on Dec 6, 2012 9:46 AM
  • 3. Re: 11g clone (mystical RMAN-05575: CONTROLFILE issue)
    Shivananda Rao Guru
    Currently Being Moderated
    Hi Mike,

    The controlfile backup must also be available in the backup location that you mention in the duplicate command.
    RMAN-05575: CONTROLFILE backup created before TO_DATE('20121205:09:13:00','YYYYMMDD:HH24:MI:SS') not found in /nfs_orawork/BACKUP/CSPRODA1
    The until time you have mentioned does not have the controlfile backup that falls within this time. You need to set the until time clause with a value that has the control file backup.


    Regards,
    Shivananda
  • 4. Re: 11g clone (mystical RMAN-05575: CONTROLFILE issue)
    Dird Pro
    Currently Being Moderated
    Hi,

    OK. Any other ideas? :)

    Mike
  • 5. Re: 11g clone (mystical RMAN-05575: CONTROLFILE issue)
    tychos Expert
    Currently Being Moderated
    Hi Mike,
    Do you have the controlfile autobackup configured to on in rman?
    (If you have it set it will automatically generate a controlfile backup and if you use disk backups also set the location.)
    You can check this with:
    show all;
    Please enable it with:
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    and run a new backup and duplicate.
    Let us know the result.
    Rgds,
    Tycho
  • 6. Re: 11g clone (mystical RMAN-05575: CONTROLFILE issue)
    Dird Pro
    Currently Being Moderated
    It looks like it's working now by removing all but one control file and removing the UNTIL TIME setting. Won't know until later if it complains about missing archive log files present in the control file or not. Would block change tracking need to be disabled on the target server when using BACKUP LOCATION? It's my understanding that it doesnt touch the target server at all? (only using rman auxiliary /) but it has still been disabled on prod for now, I'm guessing because of this being ap problem with previous techniques but not with 11g with BACKUP LOCATION?

    Mike

    Edited by: Dird on Dec 6, 2012 2:46 PM

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points