Failover Configuration in Oracle11g

Hi Gurus,
Can anyone please guide me to get a good documentation for failover configuration?
DB Version: Oracle11g
OS: Microsoft XP
//saby

Hi,
According to the doc I have configured the standby DB but when issuening:
select sequence#, applied from v$archived_log
order by sequence#;
I am getting "NO" for applied column.
Also when trying to "alter standby database open read only;" it gives:
error on system01.dbf. file is lock.
Can anyone please tell where I have done the mistake?
//saby

Similar Messages

  • Warning: ORA-16829: fast-start failover configuration is lagging

    Hi
    I got waring for fast_start failover configuration
    DGMGRL> show configuration
    Configuration - activefailover_migdb
    Protection Mode: MaxPerformance
    Databases:
    migdb - Primary database
    Warning: ORA-16829: fast-start failover configuration is lagging
    migdbdr - (*) Physical standby database
    Warning: ORA-16829: fast-start failover configuration is lagging
    Fast-Start Failover: ENABLED
    Configuration Status:
    WARNING
    anybody please suggest solution for the same

    Dear shd,
    Please check the following link;
    http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28419/d_dg.htm
    *ORA-16829: lagging Fast-Start Failover configuration*
    +DBMS_DG.INITIATE_FS_FAILOVER was invoked in a maximum performance fast-start failover configuration when the configuration was not in the user-specified redo lag limit.+
    Oracle Error :: ORA-16829
    fast-start failover configuration is lagging
    Cause
    The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property. As a result, a fast-start failover could not happen in the event of a primary database failure.
    Action
    Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully trasmitting redo data. If this condition persists consider raising the value of the FastStartFailoverLagLimit configuration property.
    Ogan

  • Failover Configuration

    For failover configuration with Oracle 9i I have used
    two database in same m/c. and the listner.ora is as following :-
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC3))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = tcs052640)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = D:\oracle\ora_home)
    (PROGRAM = extproc)
    (SID_DESC =
    (ORACLE_HOME = D:\oracle\ora_home)
    (SID_NAME = SPACE)
    (SID_DESC =
    (ORACLE_HOME = D:\oracle\ora_home)
    (SID_NAME = UIIVS2)
    And TNS Entry which i have used in a m/c. which has only oracle client is like the following :-
    PROD.WORLD =
    (DESCRIPTION_LIST =
    (FAILOVER = TRUE)
    (LOAD_BALANCE = FALSE)
    (DESCRIPTION =
    (ADDRESS =
    (PROTOCOL = TCP)
    (HOST = TCS052640)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = SPACE.WORLD)
    (SERVER = DEDICATED)
    (DESCRIPTION =
    (ADDRESS =
    (PROTOCOL = TCP)
    (HOST = TCS052640)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = UIIVS2.WORLD)
    (SERVER = DEDICATED)
    Now i am connected to SPACE from that m/c. which has only Oracle 9i client and then shutdown the database SPACE, but
    after shutting down client is not dynamically connecting to the database UIIVS2,though I have written "FAILOVER = TRUE" in tnsnames.ora.
    It is giving error like :-
    ORA-12571: TNS:packet writer failure
    ORA-03114: not connected to ORACLE
    & when I am attempting test connection it is giving error
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    What more I have to do for connecting dynamically UIIVS2 when SPACE is down.
    If the database located in separated m/c. is there anything more need to do.
    Thanks in advance.

    Guys,
    have successfully done the failover, the failover parameter should be ON in the tns entries - thanks a lot for all of ur help.
    Regards,
    Prasenjit

  • Removing Meeting Place 6 Audio Server Failover Configuration

    Hi, I have an old MeetingPlace 6 system.
    Issue - Intermittently users are getting static and dead-air experience. Looking at Call Manager CDR, the call is trying to route to offline audio server. I verified the IPGateways for failover Audio server configuration and did not find so.
    Requirement - I would like to remove the failover configuration sine failover server is offline
    Considerations - How do I do this? What do I have to consider?
    Thanks in Advance,
    Amish                  

    Hi Andrew
    I have looked at both the suggestions from you and jdedell12.
    1. Shadow Server - there is nothing configured
    2. H.323 on CUCM - I have two IP GW's configured. Nothing else relevant to Shadow server.
    3. IP GW's - Checked GW SIM config
    Interestingly enough, after the Audio server power cycle the issue fixes itself.....I have had this issue twice in the past 9 weeks....random behaviour.
    If this occurs again, I am going to reconfigure the GW SIM in the IP GW's. Since IP GW's route the calls, I am thinking that there may be a bad configuration issue here. This is going to be the next area for look out.
    Thoughts?
    Thanks guys
    Amish

  • Cisco UNITY Failover Configuration with no Computer Browser Service

    Hi,
    Actually i'm configuring a unity failover server with version 7, at this point i'm triyng to add the failover server thru the failover configuration wizard which should list the failover server, but in this customer as a domain policy the computer browser service is disabled, reason why the failover server does not appear on the list of computers.
    Does any one have any idea on how to deal with this issue?
    Thanks.

    Javier,
    You can follow the steps here:
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsy40909
    Hope that helps,
    Brad

  • Storedge 3510 failover configuration with 1 host

    I people.
    I'm new to the storedge configuration.
    I have a Sun storedge 3510 - 2 controllers with 2 x host port fc and 1x drive port each.
    I want to do a simple configuration - connect 1 host to the storedge with failover.
    It's correct to connect the 2 controllers using the drive port - because i want failover?
    It's possible to use only 1 pci single FC adapter in the machine?
    I will connect the machine with the storedge usinge 1 fibre cable,
    I will use the host port FC1. And to do the failover I will connect the 2 controllers
    using the drive port fc3 e fc2. - THIS IS CORRECT?
    My problem is who to connect the cables and who to configure the storedge. I'm
    already connected to the COM Port.
    Another thing i have in the first controller amber light - this is a hardware problem?
    And wath is the best configuration to use with 3510 storedge, one host, and failover?
    Thank you. I need this help for now.. Please.

    Isn't it wonderful when people respond?
    I, too, am running into the same scenario. We have a single 3510FC that is connected to a single host through two controller cards. The drives are configured as a single logical drive under RAID-5. We want to have this configuration multi-pathed for redundancy, not throughput, even though controller cards NEVER fail. [sarcasm] We will be using Veritas VxVM DMP for redundancy.
    Unfortunately, I can only ever see the logical drive/LUN on one controller. The main connection is channel 0 of the primary controller. Whenever I try to configure it to simultaneously be on channel 5 of the secondary controller, the 3510 won't let me do it. I can't figure out how to get the LUN to be assigned to two host channels when one is on the primary controller and one is on the secondary controller.
    I find this to be absurd. Controllers fail. That's all that there is to it. Yet the design of the 3510 (and the 3310 as well) seem to fight like hell whenever you want to spread the logical drives across physical controllers.
    What's the solution to this one, guys?

  • Cisco call manager Network Failover Configuration

    Hi all,
    I have a cisco call manager 6.0.
    The server is configured and is functioning very well.
    Only  today I realized that the server MCS has two NIC and there is the  possibility to configure a networ failover by cli interface.
    Now the question are:
    is it possible to configure this function now without problem?
    if yes what are the ordered steps to follow?
    Thanks all.

    Hi
    you can use EtherChannel, 2 phisical ports as 1 logical

  • WLC Failover configuration

    Hello,
    I want to deploy two wlc 5508 running Software Version                 7.0.116.0 in failover mode.
    I read the documentation and I read that the two wlc must have the same configuration.
    I want to be sure that I've well understood.
    For all the interfaces, each appliance must have a different IP. I mean if WLC1 have the interface "ap-manager" "management" and "dynamic interfaces" in .1, I suppose that WLC2 should have the same interfaces with .2 IP.
    Am I right?
    By advance thanks

    The 5508 does not have an ap-manager unless you specifiacally create one.  I would not create one and use the default management interface. 
    Yes the WLC's should have the exact same config, except for the interfaces ip address and of course the hostename.
    Hostname: WLC1
    Management IP: 10.200.100.5
    Virtual: 1.1.1.1
    Dynamic Interface 1: 10.200.105.5
    Dynamic Interface 2: 10.200.110.5
    Hostname: WLC2
    Management IP: 10.200.100.6
    Virtual: 1.1.1.1
    Dynamic Interface 1: 10.200.105.6
    Dynamic Interface 2: 10.200.110.6

  • WiFi Controller 2504 Failover configuration

    Hi Mates,
    one of our customer has an AIR-CT2504-15-K9 which is used to manage 15 Access Points in his Head Office.
    They are now procuring another controller (AIR-CT2504-25-K9) to manage around 24 AP's in their warehouse.
    There is a leased line as well as site to site wireless connectivity between both these sites.
    The wireless network in the warehouse is very critical. They would like to have a controller failover of their warehouse APC to the one in the HQ. can you please suggest if this can be done. if so what would they need to procure like additional licenses.
    Thanks in Advance
    MM

    Hi Mitdhun,
    The 2504 requires license for access points. The 2504 doesn't support HA(It can support with 7.5 version)  which is what you are describing.
    If you older image(less then v7.5)
    Then
    Your better off just having ap license on both the 2504 and configure as primary and secondary WLCs.
    If you have v7.5 then: read this and configure accordingly.
    https://supportforums.cisco.com/docs/DOC-26827
    http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bd3504.shtml
    Hope it helps.
    Regards

  • FWSM Failover configuration - One Context

    Hi,
    Is it possible to configure only one context in H.A. in FWSM? , yesterday  I tried to configure this but I can´t .
    Please check my configuration and tell me your opinon, or not is possible ,  maybe I have to configure all context in H.A.
    This message appears in the console when I active the FAILOVER
    Nov 23 2011 19:20:04: %FWSM-1-105002: (Secondary) Enabling failover.
    Nov 23 2011 19:20:08: %FWSM-1-105038: (Secondary) Interface count mismatch
    Nov 23 2011 19:20:08: %FWSM-1-104002: (Secondary) Switching to STNDBY - Other unit has different set of vlans configured
    Nov 23 2011 19:20:11: %FWSM-1-105001: (Secondary) Disabling failover.
    Nov 23 2011 19:23:58: %FWSM-6-302010: 0 in use, 46069 most used
    FWSM-Primario# show failover
    Failover On
    Failover unit PrimaryFailover LAN Interface: FAILLINK Vlan 1100 (up)
    Unit Poll frequency 1 seconds, holdtime 15 seconds
    Interface Poll frequency 15 seconds
    Interface Policy 50%
    Monitored Interfaces 1 of 250 maximum
    failover replication http
    Config sync: active
    Version: Ours 4.1(5), Mate 4.1(5)
    Last Failover at: 19:18:35 UTC Nov 23 2011
            This host: Primary - Active
                    Active time: 1125 (sec)
                    admin Interface inside (10.1.1.1): Normal (Not-Monitored)
                    admin Interface outside (20.1.1.1): No Link (Not-Monitored)
                    FW-GoB-Fija Interface WASOB2N-SISOB2N-Fija (10.115.30.36): Normal (Waiting)
                    GESTION-WAS Interface OUTSIDE (10.116.20.22): Normal (Not-Monitored)
                    GESTION-WAS Interface U2000 (10.123.20.1): Normal (Not-Monitored)
            Other host: Secondary - Cold Standby
                    Active time: 0 (sec)
                    admin Interface inside (0.0.0.0): Unknown (Not-Monitored)
                    admin Interface outside (0.0.0.0): Unknown (Not-Monitored)
                    FW-GoB-Fija Interface WASOB2N-SISOB2N-Fija (10.115.30.37): Unknown (Waiting)
                    GESTION-WAS Interface OUTSIDE (0.0.0.0): Unknown (Not-Monitored)
                    GESTION-WAS Interface U2000 (0.0.0.0): Unknown (Not-Monitored)
    Stateful Failover Logical Update Statistics
            Link : STATELINK Vlan 1101 (up)
            Stateful Obj    xmit       xerr       rcv        rerr     
            General         0          0          0          0       
            sys cmd         0          0          0          0       
            up time         0          0          0          0       
            RPC services    0          0          0          0       
            TCP conn        0          0          0          0       
            UDP conn        0          0          0          0       
            ARP tbl         0          0          0          0       
            Xlate_Timeout   0          0          0          0       
            AAA tbl         0          0          0          0       
            DACL            0          0          0          0       
            Acl optimization        0          0          0          0       
            OSPF Area SeqNo         0          0          0          0       
            Mamba stats msg         0          0          0          0       
            Logical Update Queue Information
                            Cur     Max     Total
            Recv Q:         0       0       0
            Xmit Q:         0       0       0
    FWSM-Primario# 
    FWSM-Primario#
    The configuration in the SW-6500
    SW-PRIMARY#sh run | in fire
    firewall multiple-vlan-interfaces
    firewall module 3 vlan-group 1,2
    firewall vlan-group 1  10,20,25,400,1709
    firewall vlan-group 2  1100,1101,1111,1112
    SW-SECUNDARY#sh run | in fire
    firewall multiple-vlan-interfaces
    firewall module 3 vlan-group 1,2
    firewall vlan-group 1  900,1709
    firewall vlan-group 2  1100,1101,1111,1112
    ip subnet-zero
    FWSM-Primario(config)# sh run
    : Saved
    FWSM Version 4.1(5) <system>
    resource acl-partition 12
    hostname FWSM-Primario
    hostname secondary FWSM-Secundario
    domain-name cisco.com
    enable password 8Ry2YjIyt7RRXU24 encrypted
    interface Vlan10
    interface Vlan29
    shutdown
    interface Vlan400
    interface Vlan1100
    description LAN Failover Interface
    interface Vlan1101
    description STATE Failover Interface
    interface Vlan1111
    description FWSW_7200_GoB_Fija
    interface Vlan1112
    description FWSW_7200_GoB_BA
    interface Vlan1709
    passwd 2KFQnbNIdI.2KYOU encrypted
    class default
      limit-resource IPSec 5
      limit-resource Mac-addresses 65535
      limit-resource ASDM 5
      limit-resource SSH 5
      limit-resource Telnet 5
      limit-resource All 0
    ftp mode passive
    pager lines 24
    failover
    failover lan unit primary
    failover lan interface FAILLINK Vlan1100
    failover replication http
    failover link STATELINK Vlan1101
    failover interface ip FAILLINK 10.115.30.17 255.255.255.252 standby 10.115.30.18
    failover interface ip STATELINK 10.115.30.21 255.255.255.252 standby 10.115.30.22
    failover group 1
      preempt
      replication http
    no asdm history enable
    arp timeout 14400
    console timeout 0
    admin-context admin
    context admin
      allocate-interface Vlan10
      allocate-interface Vlan29
      config-url disk:/admin.cfg
    context GESTION-WAS
      allocate-interface Vlan1709
      allocate-interface Vlan400
      config-url disk:/GESTION-WAS
    context FW-GoB-Fija
      allocate-interface Vlan1111
      allocate-interface Vlan1112
      config-url disk:/FW-GoB-Fija.cfg
      join-failover-group 1
    prompt hostname context
    Cryptochecksum:8b5fabc676745cfbafd6569c623a98b1
    : end
    SECUNDARY FIREWALL.
    FWSM# sh run
    : Saved
    FWSM Version 4.1(5) <system>
    resource acl-partition 12
    hostname FWSM
    domain-name cisco.com
    enable password S13FcA2URRiGrTIN encrypted
    interface Vlan100
    shutdown
    interface Vlan900
    interface Vlan1100
    description LAN Failover Interface
    interface Vlan1101
    description STATE Failover Interface
    interface Vlan1111
    interface Vlan1112
    interface Vlan1709
    passwd 2KFQnbNIdI.2KYOU encrypted
    class default
      limit-resource IPSec 5
      limit-resource Mac-addresses 65535
      limit-resource ASDM 5
      limit-resource SSH 5
      limit-resource Telnet 5
      limit-resource All 0
    ftp mode passive
    pager lines 24
    no failover
    failover lan unit secondary
    failover lan interface FAILLINK Vlan1100
    failover replication http
    failover link STATELINK Vlan1101
    failover interface ip FAILLINK 10.115.30.17 255.255.255.252 standby 10.115.30.18
    failover interface ip STATELINK 10.115.30.21 255.255.255.252 standby 10.115.30.22
    failover group 1
      preempt
      replication http
    no asdm history enable
    arp timeout 14400
    console timeout 0
    admin-context PCBA-NAT
    context PCBA-NAT
      allocate-interface Vlan1709
      allocate-interface Vlan900
      config-url disk:/PCBA-NAT
    context FW-GoB-Fija
      allocate-interface Vlan1111
      allocate-interface Vlan1112
      config-url disk:/FW-GoB-Fija
      join-failover-group 1
    prompt hostname context
    Cryptochecksum:c7529707b6d10d02c296a57253a925b2
    : end
    FWSM#
    I WILL APRECIATE YOUR COMMENTS, BECAUSE IT´S IMPORTANT , THE FWSM SUPPORT FOR DEFAULT 3 CONTEXT.
    Regards,
    Robert Soto.

    Hi Robert,
    Unfortunately no, this is not possible.
    Since you enable failover at the system level, all contexts will particpate in failover and there is no way to change this.
    Additionally, both firewalls in the failover pair must have identical licenses, VLANs, and software versions in order for failover to work properly.
    -Mike

  • DHCP Failover configuration.

    Dear Team,
         As per the requirement i've created 10 VLANs. and also configued HSRP for failover. Out of 10 Vlans we have configured DHCP for 2 VLANs in the active switch.
    My concerns:
    1. Do we have to configure DHCP in standby switch too?
    2. If yes, is there any Active and Standby concept for DHCP?
    Switch Model:
    WS-C4506-E
    Regards,
    Vamsi Harish.T.
    [email protected]

    Hi,
    The Host sends a DHCP broadcast request message to the Active Switch whenever it needs to assign and get an ip address based on the DHCP release confguration on the DHCP server or when the Hosts Got shut down. So yes there is a Concept here, the Concept is that the Active Switch will always get the DHCP request from the HOST. However, if the Active Switch fails, The HOSTS will be sending the DHCP broadcast request messages to the Standby Switch which becomes the Active one now, and if there is no DHCP service configured on the Standby Switch, then Hosts will fail to assign/Got an IP addresses. This Means both Active & Standby Switches should be configured with DHCP.
    HTH
    Mohamed

  • ASA 5550 failover configuration

    I have two identical ASA 5550 firewalls that I need to set up for Active/Standby failover so I can then upgrade them with zero downtime.  I am running them in single, routed mode so I would have to configure failover for Active/Standby.  Can I do a cable-based configuration? The documentation states that is only available on the PIX 500 Security Appliance.  Going through the Support Community forums it appears I can.  Who is right?  If I can do cable-based configuration do I have to turn off the secondary ASA to do the inital configuration?  Thanks much.

    Hello James,
    Yes, you can do cable-based (if you mean connect the devices via a cable without a switch.. That will not be a problem)
    Cisco recommends use a switch between the units for troubleshooting purposes but it's not a MUST.
    Configuration wise, same procesure nothing different so just follow the regular process.
    For more information about Core and Security Networking follow my website at http://laguiadelnetworking.com
    Any question contact me at [email protected]
    Cheers,
    Julio Carvajal Segura

  • Agent Failover Configuration

    Hello,
    I am trying to configure agent failover. I am using the script provided my Microsoft, see here:
    http://technet.microsoft.com/en-us/library/hh212733.aspx
    This is the script I am using:
    $primaryMS = Get-SCOMManagementServer –Name “Server1.domain.net”
    $failoverMS = Get-SCOMManagementServer –Name “Server2.domain.net”
    $agent = Get-SCOMAgent –Name “Agent.domain.net”
    Set-SCOMParentManagementServer –Agent $agent –PrimaryServer $primaryMS
    Set-SCOMParentManagementServer –Agent $agent –FailoverServer $failoverMS
    I execute the PS1 script, and no errors return, great. However, I go back to my agent, and the Operations Agent is still only listing Server1 as its Reporting Server.
    Is there any way to verify what I just execute, actually worked, other than turning off Server1 to test true failover?
    I am assuming my script works, if it looks wrong, please let me know.
    I am running SCOM 2012 SP1.
    Thanks everyone.

    Glad to see you resovled the issue and thanks for sharing the resolution.
    Niki Han
    TechNet Community Support

  • Failover configuration in veritas clusters

    Hi ,
    did any body knows about configuring failover in veritas clusters.
    i have 3 machines (v240) to be installed VCS3.5 AND HAVE TO CONFIGURE 3 RD NODE AS FAILOVER FOR THE 1ST AND 2 ND node .....can you guys please let me know hoewto configure this scenarion , it is on solaris9.
    appreciated.
    srayup

    This is a Sun forum, so your unlikely to get many responses on Veritas Cluster s/w which is not supported by Sun.
    However to answer your question:
    When you configure the Service Group on the 2 primary nodes you have to specify the SystemList parameter in the main.cf config file. To create a N+1 Symmetric VCS Config as you have started simply specify the failover node in the systemlist and the primary node in the autostartlist.
    e.g. in the main.cf file on both primary nodes would look like this:
    group group_name (
    SystemList = { primarynodeA, secondarynode }
    AutoStartList = {primarynodeA}
    This specifies for the service group that primarynodeA will be the preferred host to start the app, whilst the posible failover nodes are secondarynode.
    You can't specify failover at a node level, but at a service group level.

  • RV320 router failover configuration

    Hello,
    I have an RV320 router with a WAN connection to the office LAN and a 3G USB modem for failover.
    However the failover doesn't work well.
    When I unplugged the cable to WAN it works as expected, the 3G modem take over within a couple of seconds.
    But when I have trouble with overseas connection, the WAN is still up and the router doesn't switch to the 3G modem.
    Is it possible to configure the router so that it ping a specific IP regularly and if the ping fails, it switch to the 3G connection?
    Thanks.

    The setting you need is under System Management > Dual WAN 
    -Select WAN 1 and click edit.  
    --Under Network Service Detection you can specify an internet host to act as the trigger for failover.

Maybe you are looking for