If you want to service the primary server, you can switchover to the standby server.
The public listener on the current standby server has not been set. To avoid IMPAX Client connectivity problems, you must stop listener_public on the primary server when the primary database goes down. You can then switchover to the standby server, run the standby database, and reinstate the former primary server. During this time, the IMPAX Client can still connect to the database, which is running on the standby Oracle Data Guard host.
To switch over to the standby server
Stop the public listener on the primary server.
On Solaris, as the oracle user, type lsnrctl stop listener_public. On Windows stop the public_listener service.
To stop IMPAX on the primary server, as the root user, type
stop_impax (Solaris) or stopall (Windows)
To launch the Data Guard manager on the primary server and perform the switchover, as the Oracle user, type
dgmgrl sys/stayout@mvf1
show configuration
switchover to 'MVF2'
show configuration
exit
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.
To query for the ae_ref and the ae_title, in CLUI, type
ae query
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_failed_primary_server'
Two service refs are returned.
For each service ref, in CLUI, type
service delete service_ref
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'
To start IMPAX on the new primary server, as the root user, type
start_impax (Solaris) or startall (Windows)
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: If this is the first time that the standby database is opened after a switchover, 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.