Forum Stats

  • 3,770,332 Users
  • 2,253,095 Discussions
  • 7,875,405 Comments

Discussions

Rollforward a L0 backup with Archivelogs

User_OO2F8
User_OO2F8 Member Posts: 23 Red Ribbon
edited Jun 28, 2020 6:32AM in Recovery Manager (RMAN)

Hello,

We have a database "A", where we cannot make any configuration changes.

A level 0 backup of "A" was taken and a database "B" is created from that backup on another server. The requirement here is to keep rolling forward database "B" with either incremental backups or archives of database "A".

However we keep getting that archivelog is no longer needed for recovery when trying to apply the newly generated archivelogs. Is there any way to keep the database "B" rolling forward?

RD

T.BoydUser_OO2F8

Best Answer

  • Dude!
    Dude! Member Posts: 22,826 Black Diamond
    edited Jun 27, 2020 2:50AM Accepted Answer
    2937552 wrote:No particular reason, I find more control with recovery through sqlplus.

    You don't need more control.

    Please see my previous response. Does this apply? If that doesn't apply, you probably don't have any problem and the message means that it found an archivelog that simply does no longer need to be applied. Try the recovery using RMAN, which is more user friendly.

    User_OO2F8User_OO2F8
«1

Answers

  • EdStevens
    EdStevens Member Posts: 28,533 Gold Crown
    edited Jun 25, 2020 9:09AM
    2937552 wrote:Hello, We have a database "A", where we cannot make any configuration changes. A level 0 backup of "A" was taken and a database "B" is created from that backup on another server. The requirement here is to keep rolling forward database "B" with either incremental backups or archives of database "A". However we keep getting that archivelog is no longer needed for recovery when trying to apply the newly generated archivelogs. Is there any way to keep the database "B" rolling forward?RD

    We don't know exactly what you've done, but the requirement you describe looks like a perfect match for Data Guard. Have you looked into that?

  • Dude!
    Dude! Member Posts: 22,826 Black Diamond
    edited Jun 25, 2020 9:23AM

    Can you show us the exact error message?

    You can usually restore a database and continue restoring using incremental level backups and archivelogs, but only until you open the database. Since you restore and recover the database on another server, using a "hot" backup, you will have to open the database using "alter database open resetlogs", which creates a new database incarnation and resets the log sequence to 1. You would have to reset the incarnation and restore from backup in order to continue applying recovery.

  • User_OO2F8
    User_OO2F8 Member Posts: 23 Red Ribbon
    edited Jun 25, 2020 11:27PM

    Hi,

    Sorry the messages are all in french.,,

    SQL> recover database using backup controlfile until cancel;

    ORA-00279: changement 13746170978152 genere a 06/24/2020 18:10:06 requis pour

    thread 1

    ORA-00289: suggestion :

    +DG_TEST_SAVE_1/TEST/ARCHIVELOG/2020_06_25/thread_1_seq_18079.275.1043995799

    ORA-00280: le changement 13746170978152 pour le thread 1 se trouve au no de

    sequence 18079

    ORA-00278: le fichier journal

    '+DG_TEST_SAVE_1/TEST/ARCHIVELOG/2020_06_25/thread_1_seq_18078.273.1043995215'

    n'est plus necessaire pour cette recuperation

    Indiquer le journal : {<RET>=suggere | nomfichier | AUTO | CANCEL}

  • User_OO2F8
    User_OO2F8 Member Posts: 23 Red Ribbon
    edited Jun 25, 2020 11:28PM

    Yes, a DG is an ideal approach. However we do not have access or privileges on the source.

  • Dude!
    Dude! Member Posts: 22,826 Black Diamond
    edited Jun 26, 2020 1:04AM

    Why do you use SQL and not RMAN to recover the database?

  • User_OO2F8
    User_OO2F8 Member Posts: 23 Red Ribbon
    edited Jun 26, 2020 9:32PM

    No particular reason, I find more control with recovery through sqlplus.

  • Manu Alphonse
    Manu Alphonse Member Posts: 74 Bronze Badge
    edited Jun 27, 2020 1:32AM

    From ORA-00280, I guess that Databae B is looking for an ORL in Database A that hasn't been archived yet.

    Can you try an "ALTER SYSTEM ARCHIVELOG CURRENT" in Database A and scp the archivelogs to Database B server . Please note that, in RAC, this command will switch the logs on all RAC instances.

    Have you tried moving L1 backup pieces from Database A, then cataloging and recovering it in Database B?

    If this is going to be a daily requirement and you use enterprise SAN storage from EMC, HDS, ..etc - then you can do SAN level replication. Usually without any extra licence cost.

    Manu Alphonse

    ++Please mention DB version in future posts

    T.Boyd
  • Dude!
    Dude! Member Posts: 22,826 Black Diamond
    edited Jun 27, 2020 2:45AM

    That might be the case if an archivelog sequence cannot be found, however, here the message is "not needed."

    Btw, if you do backup plus archivelog, or backup archivelog, RMAN always archives the current redo log.

  • Dude!
    Dude! Member Posts: 22,826 Black Diamond
    edited Jun 27, 2020 2:50AM Accepted Answer
    2937552 wrote:No particular reason, I find more control with recovery through sqlplus.

    You don't need more control.

    Please see my previous response. Does this apply? If that doesn't apply, you probably don't have any problem and the message means that it found an archivelog that simply does no longer need to be applied. Try the recovery using RMAN, which is more user friendly.

    User_OO2F8User_OO2F8
  • User_OO2F8
    User_OO2F8 Member Posts: 23 Red Ribbon
    edited Jun 27, 2020 10:10PM

    Thanks, I tried recovering in rman and the message was much more user friendly. It actually applied all the archives beyond the l0 backup.

    I also found that ORA-00278 actually isn't an error, it actually applies the archive log, but a message that it's a message to let us know it's not needed.

    More info here

    https://oraclefreak.wordpress.com/2017/04/17/rman-backup-and-restore/