Dataguard switchover & failover testing

i want to build new physical & logical dbs just for testing & learning, as per menalink notes 736863.1 & 748595.1
wondering that configuration will let me test switchover & failover testing?

Hi there,
Those notes help you to build a proper data guard configuration in both Physical and Logical Standby enviromnment.
I would also recommend to check:
- [The Oracle online documentation|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/toc.htm]
- [Oracle Maximum Availability Architecture site on OTN|http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm]
These documents can provide a big picture of Data Guard configurations from different approaches as well as I would also recommend to learn and practice more advanced techniques and features such as Flasback database, Fast-start-failover or Cascaded destinations.
Hope this helps,
Good luck and regards,
Jozsef

Similar Messages

  • Dataguard switch/failover tests notes

    version 9i-11g
    somebody can share different scenarios for this testing?

    version 9i-11g
    somebody can share different scenarios for this testing?It would be precious to go through all:
    1. [Oracle10g: Data Guard Switchover and Failover Best Practices|https://metalink2.oracle.com/metalink/plsql/f?p=130:14:8262553999369510259::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,387266.1,1,1,1,helvetica]
    2. Assuming you don't have dataguard broker. [Performing Switchover in a Data Guard Configuration without the Data Guard Broker|https://metalink2.oracle.com/metalink/plsql/f?p=130:14:8262553999369510259::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,232240.1,1,1,1,helvetica]
    Regards,
    S.K.

  • Performing Switchover  Failover

    Most respected experts,
    i want to perform switchover, failover scenarios in my test dataguard environment.
    i want to know that
    1. What parameters do i need to change in parameter files, NETWORK configuration files ?
    2. Moreover my standby db in which mode ( (i) maximum performance (ii) maximum protection (iii) maximum availability
    i mean does this mode affect our failover , switchover operation.
    3.Is there any other important things which we have to follow to perform failover , switchover
    plz reply
    regards

    Rehan Tayyab wrote:
    1. What parameters do i need to change in parameter files, NETWORK configuration files ?
    You can configure network to communicate with primary site, depending on database role (using services, and triggers on db role change )
    2. Moreover my standby db in which mode ( (i) maximum performance (ii) maximum protection (iii) maximum availability
    i mean does this mode affect our failover , switchover operation.
    Switchover/failover in Maximum Protection mode will hung your env unless you set log_archive_dest_state_n pointing to your old primary to DEFER
    3.Is there any other important things which we have to follow to perform failover , switchover
    One of the most important - put Primary into Flashback mode before failover. Without Flashback you need to recreate Primary after failover.

  • Consideration of DBFS when doing a switchover/failover to standby

    Can anyone let me know if i can configure the DBFS separated from the Production database with a dataguard standby to reduce the impact on my production database?

    Hello;
    Yes. To me a failover is a last resort. Ask yourself a few questions:
    Does my business require 100 percent uptime?
    How long will the Primary not be available?
    How long and how will I recover from the failover?
    Can I do a switchover instead?
    Every year we power down the main server room for a weekend. What I do is a switchover and then a switch back after the old primary comes up as the standby and catches up.
    Here are my failover test notes:
    http://www.visi.com/~mseberg/data_guard/Data_Guard_Failover_Test_using_SQL.pdf
    This may help too:
    Rolling a Standby Forward using an RMAN Incremental Backup To Fix The Nologging Changes (Doc ID 958181.1)
    Best Regards
    mseberg

  • Primary and standby init file (switchove/failover)

    I have created standby database, its working fine, and logs are copying and being applied. I have successfully opened standby database in read only mode.
    Now I want to perform switchover and failover, please check parameters in init file that I have added.
    Primary database init file :
    *.control_files='D:\oracle\product\10.2.0/oradata/primary/\control01.ctl','D:\oracle\product\10.2.0/oradata/primary/\control02.ctl','D:\oracle\product\10.2.0/oradata/primary/\control03.ctl'
    *.db_name='primary'
    *.db_unique_name='PRIMARY'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=primaryXDB)'
    *.log_archive_dest_1='location=D:\oracle\product\10.2.0\oradata\archive'
    *.log_archive_dest_state_1=ENABLE
    *.log_archive_dest_state_2=ENABLE
    *.log_archive_dest_2='SERVICE=standby LGWR ASYNC'
    *.log_archive_format='arc_%s_%t_%r.arc'
    *.fal_client='PRIMARY'
    *.fal_server='STANDBY'
    standby database init file :
    *.control_files='D:\oracle\product\10.2.0/oradata/primary/STANDBY_CONTROL.CTL'
    *.db_name='primary'
    *.db_unique_name='STANDBY'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=primaryXDB)'
    *.log_archive_dest_1='location=D:\oracle\product\10.2.0\oradata\archive'
    *.log_archive_format='arc_%s_%t_%r.arc'
    *.log_archive_dest_state_2=ENABLE
    *.fal_server='PRIMARY'
    *.fal_client='STANDBY'
    *.standby_file_management=auto
    Please let me know if I need to add/modify any parameter to perform switchover & failover operations.
    Regards.

    Have a look on the below links:
    http://www.orafaq.com/wiki/DataGuard_implementation_for_Oracle_10gR2_
    http://emrebaransel.blogspot.com/2008/08/dataguard-switchover-guide-physical09.html_

  • DATAGUARD SWITCHOVER 절차

    제품 : ORACLE SERVER
    작성날짜 : 2002-12-11
    DATAGUARD SWITCHOVER 절차
    =======================
    I.     Failover와 Switchover의 차이점
    1.     Failover
    -     Unplanned
    -     Primary는 new standby가 될 수 없고 discard되어야 한다.
    -     Standby는 "alter database activate standby database" 명령을 사용하여
    Primary로서 Open 된다. 이 명령이 수행되는 동안 resetlogs operation이 수행되기
    때문에 primary 는 discard될 수 밖에 없다.
    -     New standby 를 생성하는데 상당한 시간이 걸리므로 그 만큼 risk에 상당시간
    노출되게 된다.
    -     Oracle 9i에서도 incomplete recovery를 위해 여전히 사용 가능하다.
    2.     Switchover
    -     Planned
    -     Primary는 discard되지 않고 new standby가 된다.
    -     Switchover는 다음과 같은 조건이 만족될 때 가능하다
    a)     Primary가 graceful shutdown 수행(normal, transactional, immediate)
    b)     Standby를 primary의 시점과 같게 만들어줄 모든Archive log가 필요하다.
    c)     Primary의 online redo log가 available해야 한다.
    NOTE:
    RAC 환경에서는 switchover operation을 위해서 오직 한 instance만이 허용된다.
    Switchover operation동안 다른 instance는 반드시 shutdown되어 있어야 한다.
    II. DATABASE SWITCHOVER STEPS
    Step 1) Switchover를 수행하는 session을 제외한 Primary database와
    standby database의 모든 session을 종료한다.
    Step 2) Primary database가 standby database로 switchover될 수 있는지를 check한다.
         SQL> select switchover_status from v$database;
    Switchover_status가 'TO STANDBY' 이면 switchover operation이 가능하다.
    그러나 'SESSION ACTIVE'라면 모든 session이 아직 종료되지 않았다는
    의미이므로 다시금 session 상태를 check하여 기타 아직 종료되지 않은
    session을 종료 시켜야 한다.
    Step 3) 다음과 같은 명령을 수행한다
    SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY;
    이 명령어는 다음과 같은 과정을 수행한다.
    -     Primary database를 close한다
    -     Unarchived log file을 archive하고 그것을 standby database에 보낸다
    -     Archiving되고 있는 마지막 log file에 END-OF-REDO marker를 더함.
    -     Current controlfile의 backup을 생성하고 current controlfile을 standby
    control file로 converion함.
    Step 4) Shutdown normal;
    Step 5) initSID.ora 안에서 primary role parameter들을 disable하고 standby
    parameter를 enable한다.
    Step 6) startup nomount;
    Step 7) alter database mount standby database;
    Step 8) Standby database가 Primary database로 switchover될 수 있는지를 check한다.
         SQL> select switchover_status from v$database;
    Switchover_status가 'TO PRIMARY' 이면 switchover operation이 가능하다.
    그러나 'SESSION ACTIVE'라면 모든 session이 아직 종료되지 않았다는 의미이므로
    다시금 session 상태를 check하여 기타 아직 종료되지 않은 session을 종료 시켜야 한다.
    Step 9) 다음과 같은 명령을 수행한다.
    ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL PRIMARY;
    이 명령어는 다음과 같은 과정을 수행한다.
    -     End-of-redo marker를 포함하고 있는 마지막 redo log를 받아서 적용한 것을
    보장한다
    -     Standby database의 read-only transaction으로 open되어 있으면 close한다.
    -     Standby control file을 current control file로 conversion한다.
    Step 10) Database를 shutdown 한다.
    Step 11) initSID.ora 에서 Primary role로 변경한다.
    Step 12) Database를 startup한다.
    Step 13) Standby database를 managed recovery mode로 바꾼다
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;
    Step 14) Primary database로부터 Standby database로 log archiving을 시도하여
    정상인지 check한다.
    Reference Documents
    -------------------

    Hi,
    since OCI library is required for TAF (transparent application failover)
    you can switchover using JDBC OCI driver, but not the THIN driver.
    Andrey

  • Switchover/Failover of Database

    HI guys
    Have implemented 10g dataguard -> all ok.
    Problem I have is if I succcessfully switchover, the standby listener still retains the active 'service_name' and the clients when connecting get ORA-01033: ORACLE initialization or shutdown in progress.
    I tried creating trigger to update service_name as per DOCO eg Note:316740.1 and http://www.lazydba.com/oracle/0__147296.html
    This doesn't seem to work. The services on both the new PROD and STDBY are still both registering the global service name with each listener - so hit the same ORA-01033: ORACLE initialization or shutdown in progress.
    Whats the normal procedure (in detail please) of allowing applications to connect to new production server after switchover/failover ?? [Justin ?]
    eg
    1) DNS
    2) SQLNET
    thanks

    HAs anyone else seen this issue - obviously I can shutdown the listener but thats not good for the broker communications - in 9i you could use a trigger - the doco says the same in 10g -> but doesn't seem to work ??
    Have raised SR also.

  • N+1 5508 WLC failover test

    Good day all,
    I have a question about the N+1 5508 failover test:
    Should I shutdown one of the primary WLC to test failover?
    I just setup the N+1 bakcup WLC (5508). B
    Based on: http://www.cisco.com/en/US/docs/wireless/technology/hi_avail/N1_High_Availability_Deployment_Guide.pdf
    We have two production WLCs both 5508 and one 4405.
    We just purchased another HA-SKU WLC 5508.
    All our four WLCs had been setup into one mobility group in version 7.4.100.6.
    Their neighbors are all up.
    But our test AP could not register to the Backup N+1 WLC. ( We are using option 43 in our DHCP server for all the AP boot.)
    Here are the log screen:
    ================ From test Access Point============
    *Mar  1 00:00:53.099: %CDP_PD-4-POWER_OK: Full power - INJECTOR_CONFIGURED_ON_SOURCE inline power source
    *Mar  1 00:00:53.842: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.255.1.3, mask 255.255.255.0, hostname wo11-test-ap1
    *Mar  1 00:00:54.188: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Mar  1 00:00:55.188: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Mar  1 00:00:55.279: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
    *Mar  1 00:00:56.280: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
    *Mar  1 00:01:03.820: %CAPWAP-5-DHCP_OPTION_43: Controller address 10.254.240.5 obtained through DHCP
    *Mar  1 00:01:03.820: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Mar  1 00:01:13.823: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Aug  2 02:30:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.254.240.5 peer_port: 5246
    *Aug  2 02:31:25.003: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
    *Aug  2 02:31:55.001: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.254.240.5:5246
    *Aug  2 02:31:55.001: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Aug  2 02:30:55.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.254.240.23 peer_port: 5246
    *Aug  2 02:30:55.490: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.254.240.23 peer_port: 5246
    *Aug  2 02:30:55.493: %CAPWAP-5-SENDJOIN: sending Join Request to 10.254.240.23
    *Aug  2 02:30:55.493: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
    *Aug  2 02:30:55.493: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
    *Aug  2 02:30:55.493: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
    *Aug  2 02:30:55.493: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.254.240.23
    *Aug  2 02:30:55.874: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Aug  2 02:30:55.931: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Aug  2 02:30:55.987: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller WG-WLC1
    *Aug  2 02:30:56.041: ac_first_hop_mac - IP:10.255.1.1 Hop IP:10.255.1.1 IDB:BVI1
    *Aug  2 02:30:56.041: Setting AC first hop MAC: ccef.481f.14bf
    -test-ap1#sh int bvI 1
    BVI1 is up, line protocol is up
      Hardware is BVI, address is e8b7.489e.4645 (bia e8b7.489e.4645)
      Internet address is 10.255.1.3/24
    ===================From backup N+1 WLC===
    *spamApTask4: Aug 02 11:41:09.842: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP  10:255:1:3 (58470).
    *spamApTask4: Aug 02 11:41:01.889: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP  10:255:1:3 (58470).
    *spamApTask4: Aug 02 11:40:57.912: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP  10:255:1:3 (58470).
    *spamApTask4: Aug 02 11:40:55.924: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP  10:255:1:3 (58470).
    *spamApTask4: Aug 02 11:18:50.553: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP  10:255:1:3 (58469).
    *spamApTask4: Aug 02 11:18:42.600: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP  10:255:1:3 (58469).
    *spamApTask4: Aug 02 11:18:38.623: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP  10:255:1:3 (58469).
    *spamApTask4: Aug 02 11:18:36.636: #CAPWAP-3-DTLS_DB_ERR: capwap_ac_sm.c:7305 64:a0:e7:40:eb:42: Failed to create DTLS connection for AP  10:255:1:3 (58469).
    *mmListen: Aug 02 10:43:38.637: #LOG-3-Q_IND: spam_lrad.c:1676 Ignoring discovery request from AP e8:b7:48:9e:46:45 - maximum number of downloads (0) exceeded
    *spamApTask0: Aug 02 10:43:38.500: #LWAPP-3-DISC_MAX_DOWNLOAD: spam_lrad.c:1676 Ignoring discovery request from AP e8:b7:48:9e:46:45 - maximum number of downloads (0) exceeded
    ==================== From one of our Primary WLC=====================
    (WLC-5500) >show advanced backup-controller
    AP primary Backup Controller .................... ODC-WLC1 10.254.240.5
    AP secondary Backup Controller ..................  0.0.0.0
    (WLC-5500) >show redundancy summary
    Redundancy Mode = SSO DISABLED
         Local State = ACTIVE
          Peer State = N/A
                Unit = Primary
             Unit ID = 54:75:D0:DE:DE:40
    Redundancy State = N/A
        Mobility MAC = 54:75:D0:DE:DE:40
    Redundancy Management IP Address................. 0.0.0.0
    Peer Redundancy Management IP Address............ 0.0.0.0  
    Redundancy Port IP Address....................... 0.0.0.0
    Peer Redundancy Port IP Address.................. 169.254.0.0
    (WLC-5500) >show license capacity
    Licensed Feature    Max Count         Current Count     Remaining Count
    AP Count            250               203               47
    ==============From the Backup N+1 WLC in DR =====================
    (Cisco Controller) >show redundancy summary
    Redundancy Mode = SSO DISABLED
         Local State = ACTIVE
          Peer State = N/A
                Unit = Secondary - HA SKU
             Unit ID = 6C:41:6A:5F:4C:80
    Redundancy State = N/A
        Mobility MAC = 6C:41:6A:5F:4C:80
    Redundancy Management IP Address................. 10.254.240.3
    Peer Redundancy Management IP Address............ 0.0.0.0
    Redundancy Port IP Address....................... 169.254.240.3
    Peer Redundancy Port IP Address.................. 169.254.0.0
    (Cisco Controller) >show license capacity
    Licensed Feature    Max Count         Current Count     Remaining Count
    AP Count            500               0                 500

    Current AP High Availability Configuration:
    2nd Step, shutdown the LAN Switch ports on which the Primary WLC is connected so I force the AP going to HA SKU WLC.
    DC-WiFi-SVC1-LAB(config)#inter
    DC-WiFi-SVC1-LAB(config)#interface por
    DC-WiFi-SVC1-LAB(config)#interface port-
    DC-WiFi-SVC1-LAB(config)#interface port-channel 3
    DC-WiFi-SVC1-LAB(config-if)#shut
    DC-WiFi-SVC1-LAB(config-if)#
    Log in the AP after shutdown:
    Jan 15 15:52:15.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 2)
    *Jan 15 15:52:15.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:18.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 2)
    *Jan 15 15:52:18.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:21.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 3)
    *Jan 15 15:52:21.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:24.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 4)
    *Jan 15 15:52:24.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:27.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 4)
    *Jan 15 15:52:27.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:30.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 4)
    *Jan 15 15:52:30.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:33.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 4)
    *Jan 15 15:52:33.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:36.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 4)
    *Jan 15 15:52:36.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:39.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 4)
    *Jan 15 15:52:39.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:42.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 7)
    *Jan 15 15:52:42.307: %CAPWAP-3-ERRORLOG: Retransmission count exceeded max, ignoring as the ethernet is overloaded
    *Jan 15 15:52:45.307: %CAPWAP-3-ERRORLOG: Retransmission count for packet exceeded max(CAPWAP_WTP_EVENT_REQUEST
    ., 8)
    *Jan 15 15:52:45.307: %CAPWAP-3-ERRORLOG: GOING BACK TO DISCOVER MODE
    *Jan 15 15:52:45.307: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 172.23.111.23:5246
    *Jan 15 15:52:45.371: %WIDS-6-DISABLED: IDS Signature is removed and disabled.
    *Jan 15 15:52:45.371: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
    *Jan 15 15:52:45.383: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
    *Jan 15 15:52:45.383: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
    *Jan 15 15:52:45.395: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Jan 15 15:52:46.015: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
    *Jan 15 15:52:46.383: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Jan 15 15:52:46.423: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
    *Jan 15 15:52:46.431: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
    *Jan 15 15:52:47.167: %CLEANAIR-6-STATE: Slot 0 down
    *Jan 15 15:52:47.167: %CLEANAIR-6-STATE: Slot 1 down
    *Jan 15 15:52:47.415: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Jan 15 15:52:47.423: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
    *Jan 15 15:52:47.451: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
    *Jan 15 15:52:47.459: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Jan 15 15:52:47.467: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Jan 15 15:52:48.451: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
    *Jan 15 15:52:48.459: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Jan 15 15:52:48.487: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Jan 15 15:52:49.487: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Jan 15 15:52:56.011: %CAPWAP-3-ERRORLOG: Selected MWAR 'DC-WiFi-WLC1-0'(index 1).
    *Jan 15 15:52:56.011: %CAPWAP-3-ERRORLOG: Go join a capwap controller
    *Jan 15 15:52:44.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.23.111.20 peer_port: 5246
    *Jan 15 15:52:44.467: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 172.23.111.20 peer_port: 5246
    *Jan 15 15:52:44.471: %CAPWAP-5-SENDJOIN: sending Join Request to 172.23.111.20
    *Jan 15 15:52:44.471: %CAPWAP-3-ERRORLOG: Invalid event 10 & state 5 combination.
    *Jan 15 15:52:44.471: %CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
    *Jan 15 15:52:44.471: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
    *Jan 15 15:52:44.471: %CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 172.23.111.20
    *Jan 15 15:52:44.927: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Jan 15 15:52:44.995: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Jan 15 15:52:45.003: ac_first_hop_mac - IP:10.219.96.1 Hop IP:10.219.96.1 IDB:BVI1
    *Jan 15 15:52:45.007: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Jan 15 15:52:45.075: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller DC-WiFi-WLC1-0
    *Jan 15 15:52:45.223: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
    *Jan 15 15:52:45.927: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Jan 15 15:52:45.971: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to down
    *Jan 15 15:52:45.979: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
    *Jan 15 15:52:46.007: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
    *Jan 15 15:52:46.959: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Jan 15 15:52:46.999: %DOT11-6-DFS_SCAN_START: DFS: Scanning frequency 5520 MHz for 60 seconds.
    *Jan 15 15:52:47.003: %LINK-6-UPDOWN: Interface Dot11Radio1, changed state to up
    *Jan 15 15:52:47.015: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Jan 15 15:52:47.023: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Jan 15 15:52:48.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to up
    *Jan 15 15:52:48.015: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Jan 15 15:52:48.047: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Jan 15 15:52:49.047: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    APe4d3.f11e.a8e1#         
    3rd Step, verifying the LOG on the AP and check if it can connect to the HA SKU WLC
    *Jan 15 15:52:45.075: %CAPWAP-5-JOINEDCONTROLLER: AP has joined controller DC-WiFi-WLC1-0
    *Jan 15 15:52:45.223: %WIDS-6-ENABLED: IDS Signature is loaded and enabled
    CONCLUSION:
    I needed to activate the EVALUATION LICENSE in the HA SKU WLC which had status = EULA NOT ACCEPTED. I will test the SSID's in order to confirm that redundancy using HA SKU WLC works fine.

  • VIP Failover Testing

    Hello,
    Am new to Oracle RAC. We have a 2 node 11gR2 Cluster and we are in the process of doing some failover testing. For database deployments we use an internal third part tool called the deployer which has tokens for DB configurations and the DBHost token in the deployer has the Hostname for either Node 1 or Node 2. In this way we are not actually utilising the HA feature because the connection is either to Node1 or Node 2 and if something happens to either the deployment cannot connect to the database on the respective Node which treats as a single Node instead of a Cluster.
    Instead of mentioning the DBHost value to point to the Physical Hostname of the Server in a Cluster I was thinking if I can use the VIP address i.e ipaddress-VIP for either of the Node. So after making changes I would like to do some failover testing manually and I am stuck here. How do I go about the testing scenarios.
    For Eg: if DBHOST token value is VIP for Node 2, connections are coming in to Node2 via deployer how do I proceed with the testing
    Should I bring down Node 2? If I reboot how can I see if it failed over or not to the surviving Node?
    Any help/suggestions much appreciated.
    Thanks!

    What you describe is having a RAC cluster, possibly working possibly not, and no actual use of the value of the licensing you paid for.
    My first advice to you is to read the docs and learn what RAC is, how it works, how to define and use services, and how a properly configured LISTENER.ORA and TNSNAMES.ORA should be constructed so you can compare that to what you have. With 11gR2 you should connect to the SCAN not the VIP.
    Here's how I would test RAC:
    1. Walk up to one of the servers while half the users are connected to each instance and do a SHUTDOWN ABORT. See what happens. Restart the killed node. Try it with the other node.
    2. With everything running properly and load on both machines disconnect the switch that provides the cache fusion interconnect or pull one of the cables out of the server. When you reestablish the connection what happens?
    3. Repeat #2 but this time with the connection to storage.
    The above should get you started.

  • Ise failover test

    As part of an ISE implementation, I want to test ISE failover for Admin, MnT, and PSN personas.  Does anyone have an ISE failover test plan or ISE failover test best practices documentation to share?
    Thanks much,
    David Daverso

    Steps for Administration persona failover testing
    1. Stop ISE services on Primary Admin
    Primary Admin# application stop ise
    2. Log in to the Secondary Admin GUI and manually promote to Primary
    3. Wait 10-15 minutes before process is complete
    4. Verify ISE services are up on promoted Secondary Admin
    Secondary Admin# sh application status ise
    5. Promoted Primary Admin checks
    Deployment pages shows all nodes are green and in synch
    6. User testing to verify successful authentications and logging
    Note:
    After you promote your secondary Administration node to become the primary Administration
    node, you must reconfigure your scheduled Cisco ISE backups in the newly promoted primary
    Administration node
    because scheduled backups are not replicated from the primary to secondary Administration
    node.
    7. After step 6 testing is complete restore original Primary Admin
    8. Start ISE services on original Primary Admin
    Primary Admin# application start ise
    9. Verify ISE services are up on original Primary Admin
    Primary Admin# sh application status ise
    10. Promoted Primary Admin checks
    Deployment pages shows original Primary Admin green and in synch
    11. Stop ISE services on Promoted Primary Admin
    Secondary Admin# application stop ise
    12. Log in to the original Primary Admin GUI and manually promote to Primary
    13. Wait 10-15 minutes before process is complete
    14. Verify ISE services are up on original Primary Admin
    Primary Admin# sh application status ise
    15. Promoted Primary Admin checks
    Deployment pages shows all nodes are green and in synch
    16. User testing to verify successful authentications and logging
    Note:
    After you promote your secondary Administration node to become the primary Administration
    node, you
    must reconfigure your scheduled Cisco ISE backups in the newly promoted primary
    Administration node
    because scheduled backups are not replicated from the primary to secondary Administration
    node.
    17. Start ISE services on original Secondary Admin
    Secondary Admin# application start ise
    18. Verify ISE services are up on original Secondary Admin
    Secondary Admin# sh application status ise
    19. Primary Admin checks
    Deployment pages shows original Secondary Admin green and in synch
    20. User testing to verify successful authentications and logging

  • Redundancy/failover testing

    My company is a relatively small enterprise (about 800 people scattered across 45-50 branches) and we are planning on setting up a periodic failover/redundancy testing schedule for our routers. Basically, we want to test the secondary WAN links at our branch offices and test our redundancy in our data centers.
    I'm sure there is plenty of documentation out there in regards to best practices, but what I find has more to do with a full DR test of a enterprise's systems, as opposed to a simple failover test of an office's WAN link.
    Does anyone have good suggestions for how often you should run these tests? My original thinking is to do this every quarter, but this would involve some travel for us and our resources are slim. The branch offices can be done remotely without any issue, but our DR site (which is actually used for some production traffic) would probably require one of our staff to be on site during a redundancy test.
    Thanks!

    Yep, that's what I did now.
    But keep in mind this is not really explained, even if crossing all the documentations.
    There is no document explaining what behaviour to expect in Jabber in case of redundancy of all the UC components.
    For the CUCM, it's not clear, and nothing is mentionned in case of MRA.
    IM&P is documented, but nothing for MRA.
    Expressays states about redundancy, but the behaviour to expect is not. Same for XMPP federation, no idea.
    UnityConnection as well, nothing is explained.

  • JMS queue| failover test question

    HI gurus,
    We are planning a failover test to migrate from prod to contingency environment.
    What happens to transactions that may be sitting in the JMS queue when the prod jvms are stopped? Is there a way to migrate them to the cont jvms?We are using jdbc stores and the supporting tables for both prod and cont will exist in the oracle DB, but with different names. Since the CONT jvms will be using different tables for the JMS queues, is there a way to migrate those queued transactions from prod to the CONT side?
    Details of environment
    1) OS for App Server
    Linux x86-64.
    Linux va2xpre03.gdsososos.com 2.6.18-128.1.6.el5 #1 SMP Tue Mar 24 12:05:57 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
    2) App Server type and version
    WLS 10.3.0
    JDK version
    jrockit_160_11
    3)
    Clustered and it is a Prod environment.
    Details:
    UI cluster has 5 servers. There are 4 jvms in each server. Altogether there are 20 jvms in UI cluster
    Recon cluster has 3 servers. There are 4 jvms in each server. Altogether there are 12 jvms in Recon cluster
    regards,
    Thiago Leoncio Guimaraes

    A common practice for handling this type of fail-over is to ensure that the main environment's domain name, server names, store, transaction logs (default store), and JMS configuration all all the same in the contigency environment (basically, differences, if any, are confined to things like URLs and Data Source configuration of DB location). Recovery is accomplished in the fail-over environment by copying over each server's default file store, as well as its JDBC store backing tables, prior to booting the fail-over servers.
    Transaction logs don't need to be copied over if you don't use XA (JTA) in your applications...

  • Recreate standby after failover test

    Hi -
    I'm doing a failover test for the customer:
    1. Disconnect all network between Primary and Standby
    2. On the Standby - do a failover and open it to perform application tests.
    3. After finish we need to re-create Standby again.
    Is there a way to re-create Standby again without bringing it all from backup? it's a large 2TB database and it will take hours.
    Is there a way like using flashback or other technology to do it?
    We are talking 10.2.0.3 here...
    Thanks
    Edited by: 912294 on 04:07 06/02/2012

    Is there a way to re-create Standby again without bringing it all from backup? it's a large 2TB database and it will take hours.
    Is there a way like using flashback or other technology to do it?
    We are talking 10.2.0.3 here...Its called "open the Standby database in read write mode for any reporting or testing and then move it back to standby database using the flashback technology".
    In detail check this MOS note *How To Open Physical Standby For Read Write Testing and Flashback [ID 805438.1]*
    Thanks.

  • Oracle EBS forms not working after dataguard switchover.

    Hi Guys,
    I have followed steps in document 1070033.1 to configure a data guard for R12 E-business suite and it's working properly now. i tried to perform a switchover to test the data guard, the switchover for the database tier was successful also i was able to configure and start the apps tier with no errors but when logging into the application and trying to run any form an error message is displayed saying "unable to communicate with run time process". the result of "odopmnctl status" show that all OC4Js are running and active. no errors exist in the log files. so why are the forms not running
    omari

    hi Helios,
    The error that raises up when calling the form is "FRM-92101". the application.log file shows the error stack below. your help will be appreciated.-
    formsweb: Forms session <2> exception stack trace:
    oracle.forms.engine.RunformException: Forms session <2> failed during startup: no response from runtime process
    at oracle.forms.servlet.RunformProcess.connect(Unknown Source)
    at oracle.forms.servlet.RunformProcess.dataToRunform(Unknown Source)
    at oracle.forms.servlet.RunformSession.dataToRunform(Unknown Source)
    at oracle.forms.servlet.ListenerServlet.doPost(Unknown Source)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:713)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
    at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
    at com.evermind[Oracle Containers for J2EE 10g (10.1.3.4.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
    at java.lang.Thread.run(Thread.java:736)
    regards,
    omari

  • Sap not starting during manual failover testing

    Dera friends,
    We are performing manual failover testing between CI(sap central instance) and DB(oracle database)
    the environment is ECC6.0 on AIX server
    CI is running on one server and DB is running on another, during manual testing we have failed the DB, so now DB file systems has got mounted on CI server.
    So when i log into CI with user as shown below  (sid-irp)
    su - irpadm
    and the execute the command as shown below
    irpadm 6> startsap
    i get the following message
    PRDCIXI:irpadm 6> startsap
    tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
    Checking IRP Database
    tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
    tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
    ABAP Database is not available via R3trans
    tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
    Starting SAP-Collector Daemon
    tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
    15:03:05 26.09.2008   LOG: Effective User Id is root
    This is Saposcol Version COLL 20.94 700 - AIX v10.35 5L-64 bit 070123
    Usage:  saposcol -l: Start OS Collector
            saposcol -k: Stop  OS Collector
            saposcol -d: OS Collector Dialog Mode
            saposcol -s: OS Collector Status
    The OS Collector (PID 1101932) is already running .....
    tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
    saposcol already running
    tee: 0652-044 Cannot open /home/irpadm/startsap_.log.
    ABAP Database IRP must be started on remote server
    ===============================================
    why am i getting this "ABAP Database IRP must be started on remote server" message.
    What could be the cause for my database not comming up & why is it looking for remote server, when all the DB filesystems have got mounted on CI server (the server that has CI installed)
    We are in a bad shape and the issue is quite crticial.
    Your reply would be highly appreciated.
    Regards
    Ayush

    > how can i check wether the directories are missing or not...
    mount?
    > Also how can i check it wether they are assigned to failover group or not.
    Ayush, no offense, but I suggest you contact your AIX guy and check with him together. It's very cumbersome to write down command by command, get the outpu t back and you have no clue what you are doing. Again, no offense.
    Markus

Maybe you are looking for