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

Similar Messages

  • 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

  • Enterprise Manager on Physical Standby

    Hi,
    I have switched over from my production database to the physical standby database as the production failed. When I try to use the Enterprise Manager on the new production database (previous standby) I get problems.
    Basically when I try to click on any of the links such as 'performance' etc EM attempts to log me into the old production database. I get the login screen to login to the previous production database. Seems that this information (connection string / ip address to the database) is somehow in the config. Is there anyway to reset EM to say - yes this physical standby in now in charge - please use this connection! or do I have to uninstall and re-install EM??
    Anyone ever try this.
    thx.
    S.

    Solved!
    The problem is that the standby server has a different IP address from that of the production. EM writes the IP address to some config tables so when the IP address changes you cannot use EM again until you change these values. Not documented anywhere.
    Once I changed these values everything was working as normal.

  • Avoid read-only access at physical standby

    Hi!
    DB=11.2.0.2
    when I start the standby with
    SQL> startup
    the db is open read-only.
    Is there a way to configure the db so that startup command only mounts the db and start redo apply?
    this is the config:
    DGMGRL> show configuration verbose;
    Configuration - w
    Protection Mode: MaxPerformance
    Databases:
    w_01 - Primary database
    w_02 - (*) Physical standby database
    (*) Fast-Start Failover target
    Properties:
    FastStartFailoverThreshold = '30'
    OperationTimeout = '30'
    FastStartFailoverLagLimit = '30'
    CommunicationTimeout = '180'
    FastStartFailoverAutoReinstate = 'TRUE'
    FastStartFailoverPmyShutdown = 'TRUE'
    BystandersFollowRoleChange = 'ALL'
    Fast-Start Failover: ENABLED
    Threshold: 30 seconds
    Target: w_02
    Observer: ora
    Lag Limit: 30 seconds
    Shutdown Primary: TRUE
    Auto-reinstate: TRUE
    Configuration Status:
    SUCCESS
    DGMGRL> show database w_02
    Database - w_02
    Role: PHYSICAL STANDBY
    Intended State: APPLY-ON
    Transport Lag: 0 seconds
    Apply Lag: 0 seconds
    Real Time Query: OFF
    Instance(s):
    w
    Database Status:
    SUCCESS
    br
    Daniel

    If Data Guard is setup correctly the application is not losing data, you cannot read from it, but it will apply logs:
    Ex.
    /home/oracle:STANDBY >sqlplus "/ as sysdba"
    SQL> select * from BIGSHOW.CUSTOMER;
    select * from BIGSHOW.CUSTOMER
    ERROR at line 1:
    ORA-01219: database not open: queries allowed on fixed tables/views only
    So even as the SYS user I cannot read from my test user's tables.
    ORA-01219 is expected when the standby is in this state.
    You can open READ ONLY if you have Active Data Guard, but generally that will cost you extra.
    OR, you can do thing to check your data:
    To open a standby database for read-only access when it is currently performing managed recovery:
    Cancel log apply services:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Open the database for read-only access:
    SQL> ALTER DATABASE OPEN READ ONLY;
    At some point you have start the recovery again, you probably don't have an issue.
    If you want more peace of mind on this you have to setup a test Data Guard system and bang on it.
    Best Regards
    mseberg

  • 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

  • Failover to Physical Standby

    Hi All,
    I have a configured data guard  in my local system . Please find the below configuration of the Data guard
    Data Guard Type : - Physical Standby (Oracle version 11g)
    Service Responsible for Log Transport : - ARCH
    No Standby Redo log : - Neither in Primary Nor in Standby
    I am trying to fail over by using command "alter database recover managed standby database finish"
    Please find the below alert log info after this command .
    Tue Dec 03 01:42:14 2013
    alter database recover managed standby database finish
    Attempt to do a Terminal Recovery (PRD)
    Media Recovery Start: Managed Standby Recovery (PRD)
    Fast Parallel Media Recovery enabled
    Managed Standby Recovery not using Real Time Apply
    Media Recovery Waiting for thread 1 sequence 145
    Terminal Recovery timestamp is '12/03/2013 01:42:15'
    Terminal Recovery: applying standby redo logs.
    Terminal Recovery: thread 1 seq# 145 redo required
    Media Recovery Waiting for thread 1 sequence 145
    Terminal Recovery: End-Of-Redo log allocation
    Terminal Recovery: standby redo logfile 3 created '/data/PRD_DR/arch/arch_1_0_831359165.arch'
    This standby redo logfile is being created as part of the failover
    operation.  This standby redo logfile should be deleted after the
    switchover to primary operation completes.
    Media Recovery Log /data/PRD_DR/arch/arch_1_0_831359165.arch
    Terminal Recovery: log 3 reserved for thread 1 sequence 145
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 145 Reading mem 0
      Mem# 0: /data/PRD_DR/arch/arch_1_0_831359165.arch
    Identified End-Of-Redo for thread 1 sequence 145
    Incomplete recovery applied all redo ever generated.
    Recovery completed through change 559773 time 11/23/2013 13:38:13
    Media Recovery Complete (PRD)
    Terminal Recovery: successful completion
    Resetting standby activation ID 1895332757 (0x70f87b95)
    Completed: alter database recover managed standby database finish
    Tue Dec 03 01:42:50 2013
    alter database commit to switchover to primary
    ALTER DATABASE SWITCHOVER TO PRIMARY (PRD)
    Maximum wait for role transition is 15 minutes.
    Backup controlfile written to trace file /apps/oracle/diag/rdbms/stand/PRD/trace/PRD_ora_9466.trc
    tkcrrxms: Killing 3 processes (all RFS)
    Standby terminal recovery start SCN: 559772
    RESETLOGS after complete recovery through change 559773
    Online log /data/PRD_DR/REDOLOG11.LOG: Thread 1 Group 1 was previously cleared
    Online log /data/PRD_DR/REDOLOG21.LOG: Thread 1 Group 2 was previously cleared
    Standby became primary SCN: 559771
    Tue Dec 03 01:42:53 2013
    Here my question is , why oracle implicitly creates a standby  redo log in Standby database for successful completion of 'alter database recover managed standby database finish'.
    Thanks,

    Terminal Recovery timestamp is '12/03/2013 01:42:15'
    Terminal Recovery: applying standby redo logs.
    Terminal Recovery: thread 1 seq# 145 redo required
    Media Recovery Waiting for thread 1 sequence 145
    Terminal Recovery: End-Of-Redo log allocation
    Terminal Recovery: standby redo logfile 3 created '/data/PRD_DR/arch/arch_1_0_831359165.arch'
    This standby redo logfile is being created as part of the failover
    operation.  This standby redo logfile should be deleted after the
    switchover to primary operation completes.
    Media Recovery Log /data/PRD_DR/arch/arch_1_0_831359165.arch
    Terminal Recovery: log 3 reserved for thread 1 sequence 145
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 145 Reading mem 0
      Mem# 0: /data/PRD_DR/arch/arch_1_0_831359165.arch
    Identified End-Of-Redo for thread 1 sequence 145
    Looks like, its due to the following bug.
    Bug 5889025 : FINISH FAILOVER GENERATES INCORRECT STANDBY REDO LOG.

  • Data Guard Physical Standby Failover

    I need clarification on Physical Standby Failovers. Say I have a Primary db (A) and a physical standby (B), (A) fails and (B) is now the primary, can (A) be setup to become a standby of (B)? I've read 2 different statements in Oracle 10g Data Guard Concepts and Admin
    "During failovers involving a physical standby database: In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration."
    vice
    "After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
    Much thanks.

    In all cases, after a failover, the original primary database can no longer participate in the Data Guard configuration.
    TRUE ! But this doesn't mean that you cannot make your failed primary a new standby database !.
    You can achieve this using FLASHBACK DATABASE option:
    From the documentation:
    After a failover occurs, the original primary database can no longer participate in the Data Guard configuration until it is repaired and established as a standby database in the new configuration. To do this, you can use the Flashback Database feature to recover the failed primary database to a point in time before the failover occurred, and then convert it into a physical or logical standby database in the new configuration.
    Read the following documents:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/role_management.htm#sthref995
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
    In addition to this I'd like to mention that you can achieve the same with doing an incomplete recovery instead of using FLASHBACK DATABASE.
    "After a fast-start failover occurs, the old primary database will automatically reconfigure itself as a new standby database upon reconnection to the configuration."
    TRUE. If you enable Fast-Start Failover:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/sofo.htm#CHDDFFEC
    Cheers!

  • Status of Logical Standby In case of Failover to Physical Standby

    I am using oracle 9.2.0.8 database . I have one logical and one physical standby database in place. If I perform failover to my physical standby, will my logical standby still continue to work with new primary database?

    Thank you for your kind reply.
    I performed failover to my physical standby and now archives are going on my logical standby from new primary but changes are not getting applied on my logical standby database.
    when i tried to register the logical logfile from new primary on my logical standby i am getting following error.
    SQL> ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC';
    ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC'
    ERROR at line 1:
    ORA-01287: file is from a different database incarnation

  • 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

  • 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 DB - failover setup

    Can you please help me with the following questions:
    1. XELUSP1 is Production database, XELUSS1 is physical standby database for XELUSP1. During XELUSP1 crash, we brought up XELUSS1 as primary database manually. Post XELUSP1 is back to primary, Can we use XELUSS1 as standby database as it was?
    2. What are the steps to be done in order to make XELUSS1 as primary during failover scenario from XELUSP1?
    3.What is the impact in client/server environment in 1st case? How it can be fixed?

    Hi,
    1.No, u can't use it again in case of failover but this thing is possible in switchover mode.
    2.diff commands for diff oracle version.tell me on which version u want to perform it.
    3.littile downtime when role of server becomes changing.
    Thanks
    Kuljeet

  • Failover To Physical Standby Database

    We have 3 node RAC 11.2.0.3 Primary database data guarded to a 3 node RAC 11.2.0.3 Standby database. There is an activity scheduled to perform some of order extracts in the database which is going to result in a lot of changes. Currently the discussion is on whether what should be the quickest way to go back to a point in time before the extract process starts in case of any issues. The options that we are looking at are:
    1) Create a guaranteed restore point on both the Primary and Standby and use this to flashback the database (Quick but we have had issues where in the guaranteed restore point still does not guarantee the availability of the flashback logs) - Tested
    2) Use RMAN backup from a day before to restore and recover to point in time before the extract process began (Time consuming) - Tested
    3) Use export backup to perform a redirected restore i.e import the data from before the extract process (Time consuming) - Tested
    4) Create a guaranteed restore point on both Primary and Standby, stop the Redo Apply/Ship at the time we create the guaranteed restore point and at a point we face some issue and need to go back, simply failover to the physical standby database and then reinstate the new standby database - This has not been tested yet but seems a viable option
    With regard to the point 4, note that we are not concerned about data loss as the whole point of stopping the redo apply is to prevent the standby to be caught up with Primary during the run of the extract process. The question is whether the dataguard broker will allow failover of the primary to standby, in a situation described in bullet point 4). Please advice.

    HI,
    Please check this link:
    Physical Standby Database SWITCHOVER &amp;amp; FAILOVER Operations | Talip Hakan Ozturk&amp;#039;s ORACLE BLOG
    Thank you

  • 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

  • Switchover/Failover to physical standby

    Hi All,
    I have dataguard configured between Primary and physical standby. I would like to know how can i switch over to physical stanby when the network link is down between primary and physical standby.
    I mean what steps I can follow to make physical standby to primary and primary to staandby even when the network connectivity is down between them.
    Regards,
    Raj

    user12263161 wrote:
    Hi All,
    I have dataguard configured between Primary and physical standby. I would like to know how can i switch over to physical stanby when the network link is down between primary and physical standby. You can only failover in this case, but, if you have flashback on, you can reinstate ex-Primary to standby like described [url http://nikolayivankin.wordpress.com/2012/02/14/dgmgrl-reinstating-ex-primary-to-standby-by-flashback-database-feature/]here

  • 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

  • Image Sequence Issue

    I've got some large pictures I've been asked to make into a sequence and retain as much of their quality as possible, they will be used in a PDF plan report. I started with Flash but it couldn't handle the full size images (5184x3456 - 72dpi). I've m

  • I cannot launch Firefox, because it crashes on startup

    Hello, I have problem, if I launch FIrefox, it will crash on startup, but if I will reinstall it, it still doesn´t work. Problem has started, when I actualized WIndows. I have Windows 7 and i didn´t experienced crash all time, only this time. It coul

  • Copy testcases in eManager Enterprise v. 8.20.0555

    I have to copy testcases for different test partners. e.g. 50 Testcases Testpartner 1 needs 10 of them Testpartner 2 needs all of them Testpartner 20 needs 17 of them My intention was to import the 50 testcases and then to copy them with a separate f

  • PERL script on Solaris

    My ISP is running on solaris. I have place a PERL (.pl) script which will fire a mail. He says 'Sendmail' is configured and I can create any folder and place my script and system will recognize is automatically. As we know, all the web servers will h

  • HT1544 Can I install leopard without install disks?

    I need to re-install Leopard on a friends mac. He has leopard installed atm but he doesnt have the installation disks. Is there someway to create a bootable usb maybe using the current installation? What other options I got?