IMPAX 6.5.1 Server Knowledge Base home > Oracle Server home > Maintaining Oracle Data Guard

Failing over to the standby server

If the primary server is unavailable, you can fail over to the standby server to ensure maximum availability.

To fail over to the standby server

  1. If you can connect to the primary server, stop the public listener.

    On Solaris, as the oracle user, typelsnrctl stop listener_public.

    On Windows, stop the public_listener service.

    If you cannot connect to the primary server, skip to step 3.

  2. To stop IMPAX, as the root user on the primary server, type

    stop_impax (Solaris) or stopall (Windows)

  3. To launch the Data Guard manager on the standby server and perform the failover, as the oracle user on Solaris or the AgfaService user on Windows, type

    dgmgrl sys/stayout@mvf2

    show configuration

    failover to 'MVF2'

    show configuration

    MVF2 is now the primary server.

  4. Start the public listener on the standby server, which has been promoted to the primary server.

    On Solaris, as the oracle user, type lsnrctl start listener_public. On Windows, start the public_listener service.

  5. To query for the ae_ref and the ae_title, in CLUI, type

    ae query

  6. To determine the signal translator service refs, in CLUI, type

    select map_service.service_ref from map_service inner join map_ae on map_ae.ae_ref = map_service.ae_ref inner join map_implements on map_service.service_ref = map_implements.service_ref inner join map_process on map_implements.process_ref = map_process.process_ref where map_process.process_title='MVF_SIGNAL_TRANSLATOR' and map_ae.ae_title='<AE Title of the failed primary server>'

    Two service refs are returned.

  7. For each service ref, in CLUI, type

    service delete <service ref>

  8. To set the new primary Task Scheduler, in CLUI, type

    update map_ini set ini_value='AE_title_of_new_primary_server' where ini_section='MVF_TASK_SCHEDULER' and ini_key='PRIMARY_SERVER'

    update mvf_ts_config set ae_ref='AE_title_of_new_primary_server' where ae_ref='AE_title_of_failed_server'

  9. To start IMPAX on the new primary server, as the root user, type

    start_impax (Solaris) or startall (Windows)

  10. As the root user, restart the MVF Task Scheduler on the remaining IMPAX servers such as the Archives, Network Gateways, and Curators.

    On Solaris, restart the MVF Task Scheduler by killing the process or restarting IMPAX. On Windows, restart the Mitra System Task Scheduler service.

Note:

Note:

If this is the first time that the standby database is opened after a failover, you must re-create the temporary file on the standby server.

The IMPAX Clients can now connect to the new primary database. After the switchover, the Client may continue to experience connectivity problems, specifically in the Image area, but should be resolved on its own a few minutes after switchover as IMPAX re-establishes the connection to the newly promoted database server.


See also


Topic number: 67117

Applies to: IMPAX 6.5.1 Server Knowledge Base