This discussion is archived
1 2 Previous Next 19 Replies Latest reply: Oct 19, 2012 7:38 AM by mseberg Go to original post RSS
  • 15. Re: Problem with current scn on standby database..
    Acooper Explorer
    Currently Being Moderated
    ORA-01153: an incompatible media recovery is active

    Cause

    This indicates a currently running media recovery process.

    Mostly likely you forgot to: ( befoe you tried to recover )

    SQL>alter database recover managed standby database cancel;

    Not really sure what your question is anymore.

    The TNS-12564 screams your static entry is missing or incorrect in your listener.ora. ( needed on both servers, with different sids of course )
    (SID_DESC =
           (global_dbname = PRIMARY_DGMGRL.hostname)
           (ORACLE_HOME = /u01/app/oracle/product/11.2.0)
           (sid_name = PRIMARY)
        )
    You certainly have plenty of issues.

    Good luck
  • 16. Re: Problem with current scn on standby database..
    Ecimen Newbie
    Currently Being Moderated
    Hello;

    after i added entry into listener.ora on standby database ... i can run "alter database recover managed standby database disconnect from session;" on standby database without getting error.

    but my current_scn is not still changing on standby database. any idea?

    Edited by: Ecimen on 19.Eki.2012 06:03
  • 17. Re: Problem with current scn on standby database..
    Acooper Explorer
    Currently Being Moderated
    Yes I have a pretty good idea what the issue is. But I live in a give a little get a little world.

    Lots of people have helped you but I don't see a single "helpful" answer. So your feedback to everyone is nothing is helpful. You'll get more and better help if you correct this.
  • 18. Re: Problem with current scn on standby database..
    Ecimen Newbie
    Currently Being Moderated
    sorry, i am kinda under stress , forget to mark as helpful. anyway any idea why current scn is not changing on standby database?
  • 19. Re: Problem with current scn on standby database..
    mseberg Guru
    Currently Being Moderated
    Hello again;

    Refresh my memory. You think you have a gap because the "current_scn" from v$database on the Primary does not match the "current_scn" from v$database ?

    This by itself does not indicate a problem. The standby is expected to lag behind the primary. Are you using asynchronous non-real time apply?

    Run this on the primary :

    select current_scn from v$database;

    and then run this on the primary :

    select scn_to_timestamp(<result_from_first_query>) from dual;

    Then do the same thing on the standby and post the results along with the answers to my first two questions.

    Best Regards

    mseberg
1 2 Previous Next

Legend

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