Results 1 to 11 of 11

Thread: rman error

  1. #1
    Join Date
    Aug 2010
    Posts
    8

    Unanswered: rman error

    can any one help me in this error pls


    starting full resync of recovery catalog
    RMAN-00571: ================================================== =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ================================================== =========
    RMAN-03002: failure of show command at 09/30/2010 09:21:22
    RMAN-03014: implicit resync of recovery catalog failed
    RMAN-03009: failure of full resync command on default channel at 09/30/2010 09:21:22
    RMAN-20079: full resync from primary database is not done



    thanks you

  2. #2
    Join Date
    Jun 2004
    Posts
    796
    Provided Answers: 1
    RMAN-20079: full resync from primary database is not done
    Cause: Resync from standby detected that a full resync from primary database is required. One of the following events on primary database may have caused this error: 1) one or more tablespaces or datafiles were added 2) one or more tablespaces or datafiles were dropped 3) one or more datafiles status changed
    Action: Perform full resync after connecting to primary database.
    90% of users' problems can be resolved by punching them - the other 10% by switching off their PCs.

  3. #3
    Join Date
    Aug 2010
    Posts
    8
    Quote Originally Posted by cis_groupie View Post
    RMAN-20079: full resync from primary database is not done
    Cause: Resync from standby detected that a full resync from primary database is required. One of the following events on primary database may have caused this error: 1) one or more tablespaces or datafiles were added 2) one or more tablespaces or datafiles were dropped 3) one or more datafiles status changed
    Action: Perform full resync after connecting to primary database.
    Thanks for reply

    when i do

    resync database

    it is throwing error

    can you pls give me steps to resync to primary

  4. #4
    Join Date
    Jun 2004
    Posts
    796
    Provided Answers: 1
    How about you post what steps you are taking/ what commands you are typing to produce the error? That way, people will be able to offer more specific help.
    90% of users' problems can be resolved by punching them - the other 10% by switching off their PCs.

  5. #5
    Join Date
    Aug 2010
    Posts
    8
    RMAN> show all
    2> ;

    starting full resync of recovery catalog
    RMAN-00571: ================================================== =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ================================================== =========
    RMAN-03002: failure of show command at 10/01/2010 08:34:40
    RMAN-03014: implicit resync of recovery catalog failed
    RMAN-03009: failure of full resync command on default channel at 10/01/2010 08:34:40
    RMAN-20079: full resync from primary database is not done

    RMAN> resync catalog;

    starting full resync of recovery catalog
    RMAN-00571: ================================================== =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ================================================== =========
    RMAN-03009: failure of resync command on default channel at 10/01/2010 08:35:01
    RMAN-20079: full resync from primary database is not done

    RMAN> backup current controlfile;

    Starting backup at 01-OCT-10
    starting full resync of recovery catalog
    RMAN-00571: ================================================== =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ================================================== =========
    RMAN-03002: failure of backup command at 10/01/2010 08:35:11
    RMAN-03014: implicit resync of recovery catalog failed
    RMAN-03009: failure of full resync command on default channel at 10/01/2010 08:35:11
    RMAN-20079: full resync from primary database is not done

  6. #6
    Join Date
    Jun 2003
    Location
    West Palm Beach, FL
    Posts
    2,713

    Cool Connect to primary!

    Quote Originally Posted by banumyname View Post
    can you pls give me steps to resync to primary
    Did you NOT read cis_groupie's post?
    Did you NOT understand the action required?
    Quote Originally Posted by cis_groupie
    Action: Perform full resync after connecting to primary database.
    The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

  7. #7
    Join Date
    Aug 2010
    Posts
    8
    Quote Originally Posted by LKBrwn_DBA View Post
    Did you NOT read cis_groupie's post?
    Did you NOT understand the action required?

    i dont understand the action required

  8. #8
    Join Date
    Jun 2003
    Location
    West Palm Beach, FL
    Posts
    2,713

    Angry Ok....

    Quote Originally Posted by banumyname View Post
    i dont understand the action required
    1) Logon to the primary database server
    2) Execute rman target / catalog ...
    3) resync catalog...

    Still too difficult?
    The person who says it can't be done should not interrupt the person doing it. -- Chinese proverb

  9. #9
    Join Date
    Aug 2010
    Posts
    8
    Quote Originally Posted by LKBrwn_DBA View Post
    1) Logon to the primary database server
    2) Execute rman target / catalog ...
    3) resync catalog...

    Still too difficult?

    RMAN> resync catalog;

    RMAN-00571: ================================================== =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ================================================== =========
    RMAN-03002: failure of resync command at 10/01/2010 13:51:28
    RMAN-06002: command not allowed when not connected to a recovery catalog


  10. #10
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    Code:
    RMAN> resync catalog;
    
    using target database control file instead of recovery catalog
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of resync command at 10/01/2010 11:54:47
    RMAN-06002: command not allowed when not connected to a recovery catalog
    I can also produce this error when I do not connect to recovery catalog; so what is your point?
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  11. #11
    Join Date
    Jun 2004
    Posts
    796
    Provided Answers: 1
    If you want any more help with this you're going to have to show us exactly what you are doing i.e. cut & paste output from steps given to you in LKBrwn_DBA's last post. Telling us that you're getting an error isn't very helpful - we need to see WHY you're getting an error.
    90% of users' problems can be resolved by punching them - the other 10% by switching off their PCs.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •