DBAsupport.com Forums - Powered by vBulletin
Results 1 to 6 of 6
  1. #1
    Join Date
    Sep 2000
    My production database is running on .I created a standby and it was working fine for about a month .Today suddenly the production database went down where as the standby database was doing the managed recovery .

    when I saw the alert log it show that arch ora 600 errors ..
    The fix is to apply patch set which the oracle support has said .

    Till sunday I will not be able to do this since i have to bring other database also down .

    What should i do to remove the link between the primary and the standby database

    And have only the the primary database alone ..

    I want to have only the primary database only for the time being ...

  2. #2
    Join Date
    Nov 2000
    You really don't have to do anything to get rid of STANDBY database. Primary Database is not dependent on Standby at any time.
    When you need standby database again, you need to recreate it.

  3. #3
    Join Date
    Feb 2001
    Actually I was reading oracle documentation on creating managed recovery standby database.

    I think you have to change your initSID.ora file on your primary database. i.e. log_archive_dest_2. (Not to through archivelog files onto your standby server.


  4. #4
    Join Date
    Sep 2000
    The problem is I have a standby database created .Now in the primary database i have these parameters

    log_archive_dest_2 ='SERVICE=standby'
    log_archive_dest_state_2 =ENABLE
    log_archive_dest_state_1 =ENABLE
    standby_archive_dest =/oradata/archive/sprdprod

    Can i comment these parameters and restart the database .
    Will that solve my problem

  5. #5
    Join Date
    May 2000
    fremont ca
    If arch can not trasfer to standby database your primary database will stop.
    Check listener file in which transfer of arch automaticlly to standby site is specified via parameters. ARCH =

    Also parameter, Lock_name_space in init files.

  6. #6
    Join Date
    Feb 2000
    by doing: ALTER SYSTEM set log_archive_dest_state_2=disable;
    you will no longer transfer the archived redo logs to the standby database.

    also check v$archive_dest, look at the STATUS of the standby destination (TARGET = 'STANDBY') to make sure that it is in fact disabled.

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

We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.