standby
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: standby

  1. #1
    Join Date
    Feb 2001
    Posts
    49

    Thumbs up

    Hi everybody,

    Dp any one using standby database in managed recovery mode,so that the archives from prod copied in stdby are applied automatically without dba intervention.

    I'm planning to go for that. So can anyone who is using that mode say how to accomplish that and what are the pitfalls in that where we should be care to prevent data loss.

    Detailed explanation expected.

    Thanx
    I love dba job

  2. #2
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    As for "Detailed explanation expected": Oracle manuals are sufficiently detailed regarding standby database.

    As for the pitfals: there are only a few.
    For one, automated standby can't be implemented on Standard Edition, you must have Enterprice Edition, as standard edition does not recognise the new form of archive destination parameters (LOG_ARCHIVE_DEST_n), at least not in 8.1.6.
    And one more thing that is actualy not mentioned in the docs caused me some troubles. That is, if you wan't to switch your standby from "managed recovery" mode to "open read only" mode and vice versa, you should have no job queue processes active on standby (JOB_QUEUE_PROCESSES=0), which BTW is only logical, as you actualy don't need them on standby database. You only have to remember to activate them in case you must convert your standby to primary database.

    HTH,
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  3. #3
    Join Date
    Feb 2001
    Posts
    62
    There is a good standy database doc link on this site under tech docs/dba...

  4. #4
    Join Date
    Jul 2000
    Location
    London/Manchester
    Posts
    12
    One problem I found with the standby database in Managed Recovery Mode was that even if the archived redo logs are not sent off to the standby server (because of a temporary network problem, for instance ) Oracle doesn't notice this and give you a warning. This could therefore lead to a situation where you had one or several individual logs missing, thus rendering recovery of your standby database impossible from that point. Since you wouldn't want Oracle to actually ground to a halt in the event of it being unable to archive to all of its destinations, I'm not sure what solution there could ever be to this problem.

    All of this was certainly the case when I built a standby with 8.1.5, anyway. Please let me know, anyone, if a solution has been found.


Posting Permissions

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


Click Here to Expand Forum to Full Width