Switchover to physical standby failed

Hi gurus,
Could anyone pls help for this issue, i'm working on oracle 9i dataguard in solaris box. we succesully switchover our physical standby to primary but when tried to bring back again to physical standby it is throwing an error
SQL> alter database commit to switchover to physical standby;
alter database commit to switchover to physical standby
ERROR at line 1:
ORA-16014: log 1 sequence# 91775 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/oracle/u07/oradata/odb/redo_1a.log'
ORA-00312: online log 1 thread 1: '/oracle/u08/oradata/odb/redo_1b.log'
ORA-00312: online log 1 thread 1: '/oracle/u09/oradata/odb/redo_1c.log'
Please advice
regards,
shaan

Hi,
There is already a thread which you opened Up you can reply back in that..
switchover to physical standby failed
- Pavan Kumar N

Similar Messages

  • What happens at backend when we fire alter database commit to switchover to physical standby

         Hi,
    What exactly happens at backend when we fire alter database commit to switchover to physical standby.
    how the transition happens?
    Thanks

    Hi,
    The following will happen at the backend
    1.) Notifies the primary database that a switchover is about to occur
    2.) Disconnect all users from the primary database
    3.) Generate a special redo record that signals the End of Redo (EOR)
    4.) Converts the primary database into a standby database
    5.) Once the standby database applies the final EOR record, guaranteeing that no data loss has been lost, converts the standby database into the primary database.
    The new standby database (old primary) starts to receive the redo records and continues process until we switch back again. It is important to remember that both databases receive the EOR record so both databases know the next redo that will be received.
    Regards,
    Pradeep. V

  • Problem in switchover to physical standby database

    Hi All,
    I am doing switchover from primary to physical standby database. Physical standby is in 'managed recovery' mode using real time apply and is in mount mode. I executed alter database commit to switchover to physical standby with session shutdown command. Now i am waiting for standby mrp to exit after processing eor record, but it seems mrp was hanged.
    Below is the content from standby database:
    Recovery of Online Redo Log: Thread 1 Group 5 Seq 620 Reading mem 0
    Mem# 0: /oracle/app/oracle/dbrac/th1-redo5a.log
    Resetting standby activation ID 749049115 (0x2ca5951b)
    Media Recovery End-Of-Redo indicator encountered
    Media Recovery Continuing
    Media Recovery Waiting for thread 1 sequence 621
    Archived Log entry 14 added for thread 1 sequence 620 ID 0x2ca5951b dest 1:
    Need some help to resolve.
    Thanks
    Sandy.

    Hello;
    After after you issue ( successfully ) a :
    alter database commit to switchover to physical standby with session shutdownYou need to :
    Shutdown the former primary and mount as a standby databaseCheck out my step by step :
    http://www.visi.com/~mseberg/data_guard/Data_Guard_switchover.html
    Read everything ( all the steps ) before you proceed.
    Best Regards
    mseberg

  • Create physical standby failed at destination preparation step

    I have tried several times to create a physical standby using Grid Control. Everytime, the job failed at the step "Destination Preparation". The log file indicated the following error message:
    PLS-00553: character set name is not recognized.
    This is because an extra word "PuTTY" was inserted into the spfile as shown in the following spfile, therefore, the instance cannot be started. In addition, everytime when issuing the command "cat spfilermslag.ora", the word "PuTTY" will automatically appear in the command line after the "cat spfilermslag.ora" command.
    $ cat spfilermslag.ora
    gé ú&PuTTYrmslag.__db_cache_size=150994944
    rmslag.__large_pool_size=4194304
    rmslag.__shared_pool_size=71303168
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='/u01/app/oracle/admin/rmslag/udump'
    [oracle@wppnode2 dbs]$ PuTTY
    What is going on here? How can I fix the problem?
    Thanks!

    You can still carefully use the corrupted spfile to create a pfile and start your database with teh pfile, then create spfile from the pfile.
    Make a copy of the spfilermslag.ora sand save it as initrmslag.ora. Open the spfile with notepad, carefully remove all the wrong characters at the begining and end of the file. Use the init file to startup the database
    SQL>connect sys as sysdba
    SQL>startup spfile=$ORACLE_HOME/dbs/initrmslag.ora
    SQL>create spfile from pfile;
    SQL>shutdown immediate
    SQL>startup

  • Physical standby failed to start MRP process

    Hi,
    I have a qa db which is in ASM. I have a qa standby which is a physical standby also in ASM. I added space to the primary. Unfortunately, the standby diskgroup did not have enough space and standby mrp process crashed. I edited the primary data files to release some space and tried to restart the standby but it does not seem to work.
    What next?

    Er, Can you provide more information?
    Like maybe some details from the alert logs?
    Or maybe even the error message you get when you try to restart the standby
    The more information the easier it is to debug at a distance.
    jason.
    http://jarneil.wordpress.com

  • Create Physical Standby fails

    It looks like a script that runs, Exits in the middle.
    I am able to test a disk dump and execute host commands on both the source and destination server.
    SQL*Plus: Release 10.2.0.1.0 - Production on Thu Apr 3 12:14:49 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved.
    set echo off>Connected. GridTest>GridTest>GridTest>GridTest>GridTest> 2 3 4 5 6 7 8 9 10 11 12 13 Row count
    : 1 Start printing spfile value: spfile# G:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SPFILEGridTest.ORA PL/SQL procedure successfully completed.
    GridTest>Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options SQL*Plus
    : Release 10.2.0.1.0 - Production on Thu Apr 3 12:14:50 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved.
    CONNECT sys/#GridTest# AS SYSDBA;>ORA-01012: not logged on CONNECT sys/#GridTest# AS SYSDBA;>

    Sounds like you are loosing the network connection between your OMS and
    the standby target? Check the network.
    Regards,
    Porus.

  • Test physical standby database in dataguard

    Hi all,
    I had a successfull dataguard implementation for oracle 9r2.
    Primary and standby databases are on different nodes, logs from primay are shipping and applying to physical standby database successfully.
    As these database are for oracle 11i ebs, so for testing dataguard status i had created a table manually having columns date and remarks. Periodically i insert few records in this table in primary database and then chek this tabel in standby database (by opening in read only mode).
    Now i want to test physical standby database with applications tier  but don't want to disturb origional primary database.
    as these are the normal switchover steps
    1) at primary db
    ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
    2) at standby
    ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
    3) at primary, now this will be the stand by database
    SHUTDOWN IMMEDIATE;
    STARTUP MOUNT;
    4) at standby, now this will be the primary database
    SHUTDOWN IMMEDIATE;
    STARTUP
    My concern is if i skip step 1 and 3 and only execute step 2 and 4, will that be applicable for my requirement, or there is some other way to achieve this goal.
    Regards,
    Ken

    To avoid touching the primary production DB, you may try to use the following command on your standby database side:
    alter database activate standby database;
    This will turn your standby database to primary database, however the log will be reset and this means you will need to rebuild your DR.
    Another way is to use flash back feature on your standby database, activate it and revert back to the flashback point when the DR testing is done.

  • Data Guard - MRP stuck issues on a physical standby database

    Hi,
    Oracle 11.2.0.3 DG running. When i do a switchover the physical standby database has error with following error
    ARC0: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance <primaryDB> - Archival Error
    On standby DB
    SQL>select process, thread#, sequence#, status from v$managed_standby where process='MRP0';
    PROCESS THREAD# SEQUENCE# STATUS
    MRP0 1 548 APPLYING_LOG
    So according to Oracle support link i executed following
    SQL>recover managed standby database cancel;
    SQL>recover automatic standby database;
    The above seems to resolve the issue. What is causing is this?

    Hello again;
    Those both look perfect. I combed through my notes and found nothing like this for your version.
    Yes, I would open an SR since it appears you have done everything correct.
    ORA-600 [3020] "Stuck Recovery" [ID 30866.1]
    The "Known Bugs" section of the above has a few 11.2.0.3 entries.
    Generally the MRP gets stuck because data Guard thinks there's a GAP, you run out of room in the FRA on the Standby, or redo logs are too small and the system is switching very fast.
    Best Regards
    mseberg
    Later
    Never asked you but this "log_archive_max_processes" can be set as high as 30.
    Edited by: mseberg on Jul 16, 2012 8:01 PM
    h2. Still later
    Found this which is closer :
    Bug 13553883 - Archiver stuck but no ORA-19xxx error in alert log (messages need changing) [ID 13553883.8]

  • Physical standby on 9.2 failover fails

    Hello,
    I have setup physical standby database and it seems to be transferring data correctly. I tested it also be going into read only mode and querying for changes.
    My problem is attempting to do a failover. I simply disconnect the primary to simulate the outtage and attempt to bring secondary by doing the following. Note that I tried both commit to switchover and activate standby.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
    Database altered.
    SQL> ALTER DATABASE ACTIVATE STANDBY DATABASE;
    ALTER DATABASE ACTIVATE STANDBY DATABASE
    ERROR at line 1:
    ORA-00261: log 4 of thread 1 is being archived or modified
    ORA-00312: online log 4 thread 1: '/u02/oradata/digidsgn/stdby_redo04a.log'
    ORA-00312: online log 4 thread 1: '/u03/oradata/digidsgn/stdby_redo04b.log'
    SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
    2 ;
    ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
    ERROR at line 1:
    ORA-16139: media recovery required
    The log transfer method is by LGWR...
    LOG_ARCHIVE_DEST_2='SERVICE=DIGIDSGN.STBY LGWR ASYNC NOAFFIRM'
    Primary database is in MAXIMIZE PERFORMANCE mode.
    What am I doing wrong? I do have standby logs created, on standby the names are different from the primary ones.
    Another question:
    Is the switchover/failover operation suppose to create a normal control file and normal redo logs automatically?
    thanks.

    Well, this is gonna sound crazy, but I did a fair amount of digging and realized that I couldn't re-select my system disk as my startup disk as well (Error message said "Building boot caches on boot helper partition failed"). I was thinking the installer was trying to modify some settings on my boot volume and couldn't figure out what volume my boot volume really was.
    I thought this issue and the update installer issue was related based on something in the iTunes error log looking for "Volumes/Boot OS X".
    I figured if I could fix the Startup Disk issue, the other issue would be fixed as well. So I decided to poke around and figure out why I couldn't select my boot volume in the Startup Disk Preference Pane and found these instructions:
    Create a new files in Terminal using this command:
    *sudo nano /Library/Preferences/SystemConfiguration/com.apple.Boot.plist*
    In that file, inserted the default code:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://
    www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>Kernel</key>
    <string>mach_kernel</string>
    <key>Kernel Flags</key>
    <string></string>
    </dict>
    </plist>
    Once that file was created with the proper contents, I went back to the Startup Disk Preference Pane and could select my system disk.
    At that point I attempted to install the Trackpad/Magic Trackpad Updater... and it worked! HA! Then I tried iTunes... and success was found there as well.
    Hope you have the same luck that I did...
    Cheers,
    Sapridyne

  • Creating physical standby through Cloud Control 12C fails

    Hi,
    I have a SR with MOS on physical standby setup through Cloud Control 12C. My setup is two Exadata Quarter RAC X2-2 installations and i'm setting up primary standby/between those two installations. Lets call them exa1db01(primary) and exa2db01(standby).
    I'm using Cloud version 12.1.0.2 and agents on the latest version and patch. We just upgraded before Christmas. When i try to create a physical standby it fails on the transfer stage with below error:
    "Uncaught exception in command fileTransfer: unable to instantive value javax.xml.bind.JAXBE1ement@46dd1e39 for attribute actualException"
    At the moment its sent to developement so i have to wait for a fix. The reason for posting here is that i cant believe that this is not working on Cloud Control 12.1.0.2. This is basic functionality and i'm amazed that this is a bug. Our Exadata installation is running on 11.2.0.3 BP10 so it should be fairly fresh.
    I truly believe the problems needs to be somewhere in our installation or the connectivity between our Exadata environments. Do any of you have any experience with DG through Cloud on that participial version ?
    Cheers

    Hello again;
    Check the solution in this: ( and note the multiple versions of oracle it covers )
    UNABLE TO FIND GRID INFRASTRUCTURE LISTENER (Doc ID 1483234.1)
    Best Regards
    mseberg

  • Adding a physical standby using GridControl failed

    Hi
    I am trying to add a physical standby DB to a 10.2.0.4 database.
    It failed at the end on the 'Step: Create Standby Database'
    This is the log for this step ( step #79 ) - after backing up and restoring and after the recoverDatabase step
    Output log :
    SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:13:44 2009
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    SQL> SQL> Connected.
    SQL> SQL> SQL> ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:04 2009
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    SQL> SQL> Connected to an idle instance.
    SQL> SQL> ORACLE instance started.
    Total System Global Area 3221225472 bytes
    Fixed Size          2044072 bytes
    Variable Size          2315259736 bytes
    Database Buffers     889192448 bytes
    Redo Buffers          14729216 bytes
    SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:08 2009
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    SQL> Connected.
    SQL> SQL> 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
    PL/SQL procedure successfully completed.
    SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:08 2009
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    SQL> SQL> Connected.
    SQL> SQL> SQL> ORA-01507: database not mounted
    ORACLE instance shut down.
    SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:14 2009
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    SQL> SQL> Connected to an idle instance.
    SQL> SQL> ORACLE instance started.
    Total System Global Area 3221225472 bytes
    Fixed Size          2044072 bytes
    Variable Size          2315259736 bytes
    Database Buffers     889192448 bytes
    Redo Buffers          14729216 bytes
    Database mounted.
    SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:22 2009
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    SQL> SQL> Connected.
    SQL> SQL> SQL> ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL*Plus: Release 10.2.0.4.0 - Production on Tue Jun 2 15:14:39 2009
    Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
    SQL> SQL> Connected to an idle instance.
    SQL> SQL> ORACLE instance started.
    Total System Global Area 3221225472 bytes
    Fixed Size          2044072 bytes
    Variable Size          2315259736 bytes
    Database Buffers     889192448 bytes
    Redo Buffers          14729216 bytes
    Database mounted.
    SQL> Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/system011.dbf' to '/dg2/u04/oradata/dg2/system011.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u03/oradata/dg1/system011.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/undotbs011.dbf' to '/dg2/u04/oradata/dg2/undotbs011.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u03/oradata/dg1/undotbs011.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/sysaux011.dbf' to '/dg2/u04/oradata/dg2/sysaux011.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u03/oradata/dg1/sysaux011.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/users011.dbf' to '/dg2/u04/oradata/dg2/users011.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/users011.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/netrac_data01.dbf' to '/dg2/u04/oradata/dg2/netrac_data01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/netrac_data01.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/iview.dbf' to '/dg2/u04/oradata/dg2/iview.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/iview.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/VCADMIN01.dbf' to '/dg2/u04/oradata/dg2/VCADMIN01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/VCADMIN01.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/virt_cent_admin.dbf' to '/dg2/u04/oradata/dg2/virt_cent_admin.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/virt_cent_admin.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/testdir01.dbf' to '/dg2/u04/oradata/dg2/testdir01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/testdir01.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/sunopsis.dbf' to '/dg2/u04/oradata/dg2/sunopsis.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/sunopsis.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/xpedio02.dbf' to '/dg2/u04/oradata/dg2/xpedio02.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/xpedio02.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/xpedio01.dbf' to '/dg2/u04/oradata/dg2/xpedio01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/xpedio01.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/otis02.dbf' to '/dg2/u04/oradata/dg2/otis02.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/otis02.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/otis_data01.dbf' to '/dg2/u04/oradata/dg2/otis_data01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/otis_data01.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/ne_data.dbf' to '/dg2/u04/oradata/dg2/ne_data.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/ne_data.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/iboss_dt2.dbf' to '/dg2/u04/oradata/dg2/iboss_dt2.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/iboss_dt2.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/iboss_dt1.dbf' to '/dg2/u04/oradata/dg2/iboss_dt1.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/iboss_dt1.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/iboss_dt.dbf' to '/dg2/u04/oradata/dg2/iboss_dt.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/iboss_dt.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/ARSYSTEM3.dbf' to '/dg2/u04/oradata/dg2/ARSYSTEM3.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/ARSYSTEM3.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/ARSYSTEM2.dbf' to '/dg2/u04/oradata/dg2/ARSYSTEM2.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/ARSYSTEM2.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/ARSYSTEM1.dbf' to '/dg2/u04/oradata/dg2/ARSYSTEM1.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/ARSYSTEM1.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/users01.dbf' to '/dg2/u04/oradata/dg2/users01.dbf'
    dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = '/dg1/u04/oradata/dg1/users01.dbf'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/redo01.log' to '/dg2/u04/oradata/dg2/redo01.log'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/redo02.log' to '/dg2/u04/oradata/dg2/redo02.log'
    dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE '/dg1/u03/oradata/dg1/redo03.log' to '/dg2/u04/oradata/dg2/redo03.log'
    dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 1
    dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 2
    dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 3
    dgcreate.DGgetRecoverySCN: SELECT MAX(NEXT_CHANGE#) FROM V$ARCHIVED_LOG
    dgcreate.DGrecoverStby: SELECT FILE#, NAME from v$tempfile
    dgcreate.DGrecoverStby: ALTER DATABASE RENAME FILE '/dg1/u04/oradata/dg1/temp01.dbf' to '/tmp/temp16000'
    dgcreate.DGrecoverStby: ALTER DATABASE TEMPFILE 3 DROP
    dgcreate.DGrecoverStby: ALTER DATABASE RECOVER AUTOMATIC FROM '/dg2/u01/arch/dg2' STANDBY DATABASE UNTIL CHANGE 9210711497140
    dgcreate.DGrecoverStby: ALTER DATABASE RECOVER CANCEL
    dgcreate.DGrecoverStby: ALTER DATABASE OPEN READ ONLY
    dgcreate.DGcreateSpfile: CREATE SPFILE FROM PFILE='/dg2/u01/app/oracle/product/10.2/dbs/initdg2.ora'
    dgcreate.DGaddTempfiles: ALTER TABLESPACE TEMP ADD TEMPFILE '/dg2/u04/oradata/dg2/temp01.dbf' SIZE 1212416K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE 33553408K
    SQL Error: ORA-00604: error occurred at recursive SQL level 1
    ORA-16000: database open for read-only access
    ORA-06512: at line 26 (DBD ERROR: OCIStmtExecute)
    the last line in the alert log were :
    ALTER TABLESPACE TEMP ADD TEMPFILE '/dg2/u04/oradata/dg2/temp01.dbf' SIZE 1212416K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE 33553408K
    Completed: ALTER TABLESPACE TEMP ADD TEMPFILE '/dg2/u04/oradata/dg2/temp01.dbf' SIZE 1212416K REUSE AUTOEXTEND ON NEXT 640K MAXSIZE 33553408K
    INSV started with pid=13, OS id=16351
    and the tempfile was created successfully
    Any ideas ?
    How to debug ?
    Orna

    Hi
    Just a follow up :
    the problem was with a DDL database trigger, that is not sensitive to the read only mode of the standby database
    disabling the DDL trigger solved my problem
    Orna

  • Physical standby database fail-over

    Hi,
    I am working on Oracle 10.2.0.3 on Solaris SPARC 64-bit.
    I have a Dataguard configuration with a single Physical standby database that uses real time application. We had a major application upgrade yesterday and before the start of upgrade, we cancelled the media recovery and disabled the log_archive_dest_n so that it doesn't ship the archive logs to standby site. We left the dataguard configuration in this mode incase of a rollback.
    Primary:
    alter system set log_archive_dest_state_2='DEFER';
    alter system switch logfile;
    Standby:
    alter database recover managed standby database cancel;Due to application upgrade induced problems we had to failover to the physical standby, which was not in sync with primary from yesterday. I used the following method to fail-over since i do not want to apply any redo from yesterday.
    Standby:
    alter database activate physical standby database;
    alter database open;
    shutdown immediate;
    startupSo, after this step, the database was a stand alone database, which doesn't have any standby databases yet (but it still has log_archive_config parameter set and log_archive_dest_n parameters set but i have 'DEFER' the log_archive_dest_n pointing to the old primary). I have even changed the "archive log deletion policy to NONE"
    RMAN> configure archivelog deletion policy to none;After the fail-over was completed, the log sequence started from Sequence 1. We cleared the FRA to make space for the new archive logs and started off a FULL database backup (backup incremental level 0 database plus archivelog delete input). The backup succeded but we got these alerts in the backup log that RMAN cannot delete the archivelogs.
    RMAN-08137: WARNING: archive log not deleted as it is still neededMy question here is
    1) Even though i have disabled the log_archive_dest_n parameters, why is RMAN not able to delete the archivelogs after backup when there is no standby database for this failed-over database?
    2) Are all the old backups marked unusable after a fail-over is performed?
    FYI... flashback database was not used in this case as it did not server our purpose.
    Any information or documentation links would be greatly appreciated.
    Thanks,
    Harris.

    Thanks for the reply.
    The FINISH FORCE works in some cases but if there is an archive gap (though it didn't report in our case), it might not work some times (DOCID: 846087.1). So, we followed the Switch-over & Fail-Over best practices where it mentioned about this "ACTIVE PHYSICAL STANDBY" for a fail-over if you intend not to apply any archivelogs. The process we followed is the Right one.
    Anyhow, we got the issue resolved. Below is the resolution path.
    1) Even though if you DEFER the LOG_ARCHIVE_DEST_STATE_N parameter's on the primary, there are some situations where the Primary database in a dataguard configuration where it will not delete the archive logs due to some SCN issues. This issue may or may not arise in all fail-over scenarios. If it does, then do the following checks
    Follow DOCID: 803635.1, which talks about a PLSQL procedure to check for problematic SCN's in a dataguard configuration even though the physical standby databases are no available (i.e., if the dataguard parameters are set, log_archive_config, log_archive_dest_n='SERVICE=..." still set and even though corresponding LOG_ARCHIVE_DEST_STATE_N parameters are DEFERRED).
    If this procedure returns any rows, then the primary database is not able to delete the archivelogs because it is still thinking there is a standby database and trying to save the archive logs because of the SCN conflict.
    So, the best thing to do is, remove the DG related parameters from the spfile (log_archive_config, log_archive_dest_n parameters).
    After i made these changes, i ran a test backup using "backup archivelog all delete input", the archive logs got deleted after backup without any issues.
    Thanks,
    Harris.
    Edited by: user11971589 on Nov 18, 2010 2:55 PM

  • Switchover to a Physical Standby Database

    Hello all,
    i have completed Switchover to a Physical Standby Database succesfully, there is no error in alter log file but when i fire on my new primary database " select * from dba_segments order by 2" then it give me following error
    SQL Error: ORA-00604: error occurred at recursive SQL level 1
    ORA-06553: PLS-801: internal error [56319]
    ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [], [], [], []
    ORA-06553: PLS-801: internal error [56319]
    00604. 00000 - "error occurred at recursive SQL level %s"
    *Cause:    An error occurred while processing a recursive SQL statement
    (a statement applying to internal dictionary tables).
    *Action:   If the situation described in the next error on the stack
    can be corrected, do so; otherwise contact Oracle Support.
    my database version is
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    Thank You All For Advance Response.

    Though this MOS note applies to 10.1, see if it helps,
    *ORA-06544: PL/SQL: internal error, arguments: [56319], ORA-06553: PLS-801: internal error [56319]" errors while running catupgrd.sql [ID 863633.1*
    HTH
    Aman....                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Switchover to 1 of 3 Physical Standby (oracle 10g R2)

    Hi all,
    Previously I already had done switchover primary to standby (only 1 Physical standby was in the configuration)
    now i have some additional physical standbys (3 Physical standbys)
    stby1
    stby2
    stby3
    i want to switch to stby1 ,what needs to be done at stby2,stby3 to make them capable of identifying stby1 as their new primary.
    Kindly suggest!
    Best Regards,
    Muhammad Shakeel Azeem

    921542 wrote:
    Hi all,
    Previously I already had done switchover primary to standby (only 1 Physical standby was in the configuration)
    now i have some additional physical standbys (3 Physical standbys)
    stby1
    stby2
    stby3
    i want to switch to stby1 ,what needs to be done at stby2,stby3 to make them capable of identifying stby1 as their new primary.
    Kindly suggest!
    Best Regards,
    Muhammad Shakeel AzeemAzeem,
    Welcome to OTN,
    Once you performed switchover, You need to perform changes with some parameters from standby FAL_SERVER
    Earlier this parameter points to old primary, Now after switchover you have to put service name of new primary database service.
    Also Make changes with remote destinations log_archive_dest_n with correct service names.
    Refer this manual to work with multiple standby databases.
    http://www.oracle.com/technetwork/database/features/availability/maa10gr2multiplestandbybp-1-131937.pdf

  • EM: Creation process for a physical standby DB failed with SQL Exception

    Version: EM Oracle 10.2.5 (agents running, repository running, primary db running, all targets visible and reachable with EM)
    I try to create a physical standby database with the enterprise manager and each time the process is aborted with a SQL exception during the preparation of the job by the EM. I have added a part of the OMs log containing the error at the end of the excerpt.
    =============
    2010-04-29 16:00:39,856 [EMUI_16_00_39_/console/targets] WARN pref.SubtabPref getFolders.710 - Unknown folder id: VirtualServers retrieved from repository
    2010-04-29 16:01:04,765 [EMUI_16_01_04_/console/database/dataguard/create] ERROR em.dataguard validate.1329 - CreateBean: ClassNotFoundException: null
    2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone checkSetFileError.79 - DatabaseFileAttributes.checkSetFileError(): Null database file!
    2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone setControlfiles.160 - DatabaseFileAttributes.setDatafiles(): Invalid control file!
    2010-04-29 16:02:05,492 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone getControlFileNames.616 - DatabaseFileAttributes.getDatafileNames(): null datafile names!
    2010-04-29 16:02:32,823 [Thread-28] ERROR em.jobs remoteOp.2389 - DBVerify.remoteOp(): Error: max_stamp# 6071384
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3297 - DBCloneObject.submitJobPreparation(): getMaxLogSequenceNum: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3501 - DBCloneObject.submitJobPreparation(): Exception: java.lang.Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitDBCloneJob.3716 - DBCloneObject.submitDBCloneJob(): Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:37,496 [EMUI_16_02_37_/console/database/dataguard/create] ERROR em.dataguard onEvent.1243 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    =========
    I have set the agent perl script tracing to DEBUG, but can't find any reason, why the job preparation failed.
    Has anyone an idea why the job cannot be prepared? Thanks in advance for investigation :-)

    gromit wrote:
    Is there a difference if:
    I install EM Version 10.2.0.1/10.2.0.2 -> upgrade it to 10.2.0.3 -> upgrade it to 10.2.0.5
    OR
    I install EM Version 10.2.0.1/10.2.0.2 and directly upgrade it to 10.2.0.5 ???Hi,
    Both are same. Result will be same. Finally you are reaching 10.2.0.5 version..
    But I would suggest to choose 2nd option.. i.e. install EM Version 10.2.0.1/10.2.0.2 and directly upgrade it to 10.2.0.5.
    Because it will save your time..
    Regards
    Rajesh

Maybe you are looking for

  • Error F5742 - While Releasing Billing for accounting

    Hi, We are getting an error F5742- Break down of hold back/retainage pay is allowed for only subledger accounts while releasing a billing document for accounting. We are using installment payment terms for the billing. we are not sure why system is t

  • Backup on flash drive

    Hi all, Does anyone has made a backup of Oracle Database XE (ARCHIVELOG ON/OFF) directly to a flash drive(thumb drive, dvd,etc).? Is it better to backup on the local disk first and only after that to copy the backup files to the external device? Or i

  • Mail won't send web page content or link

    I posted this the other day on the Safari site but should have posted here as well. Suddenly I am unable to forward a web page in Safari 3.12 through Mail. I get the message: "Safari couldn't create an email message because it couldn't locate an emai

  • Control of NotifyIcon in MDI Parent from MDI child (C# Express)

    I have an MDI application with a base(Parent) form (FormA) and several child forms (Form1, Form2, etc). My Parent Form (FormA) is invisible and contains a ContextMenuStrip (contextMenuStrip1) and a NotifyIcon (notifyIcon1). I have 3 Icons defined in

  • Re: cropping, clipping, scaling, printing

    Using Aperture 2.1 I am fully aware of how to use the cropping tool. I use RAW files from a Canon 30D. I print 8x10 photos and have just uploaded my first book to Apple. When I constrain the crop to 8x10 I cannot fit in the entire part of the image I