-->
edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Manually migrate the

Manually migrate the Transaction Recovery Service

Before you begin

Before you can migrate the Transaction Recovery Service to another server in the cluster, configure the managed servers in the cluster for migration. See Configure the JTA Transaction Recovery Service for migration.

In addition, configure the default persistent store so that it stores records in a shared storage system that is accessible to any potential machine to which a failed migratable server might be migrated. See Configure the default persistent store for Transaction Recovery Service migration.

You may also want to restrict the potential servers to which you can migrate the Transaction Recovery Service to only those that have access to the transaction log files. See Configure candidate servers for Transaction Recovery Service migration.


The Transaction Recovery Service is designed to gracefully handle transaction recovery after a crash. Oracle recommends that you attempt to restart a crashed server and allow the Transaction Recovery Service to handle incomplete transactions, rather than migrate the Transaction Recovery Service to another server. However, if you anticipate that the server will be unavailable for an unacceptable length of time, you can migrate the Transaction Recovery Service to another service so that the backup server can complete transaction work for the failed server.

For more information about migrating the Transaction Recovery Service, see Transaction Recovery After a Server Fails.

To migrate the Transaction Recovery Service from a failed server in a cluster:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).

  2. Make sure the failed or failing server is not running:

    1. In the Domain Structure tree, expand Environment and select Servers.

    2. If the State of the server is anything other than SHUTDOWN, shut down the server. See Shut down a server instance.

  3. Select the failed server from which you want to migrate the Transaction Recovery Service, then select the Control > Migration tab.

  4. Click Advanced to show the JTA Migration options.

  5. Under JTA Transaction Recovery Service Migration, use the Migrate to Server drop-down to select that server on which you want to migrate the Transaction Recovery Service for the current server.

    The server that you select must have access to the default persistent store (transaction log files) for the current server. The selected server will perform the transaction recovery process for the failed server.

  6. Click Save.

    A request is submitted to migrate the Transaction Recovery Service and the configuration edit lock is released. If the migration fails, an error message is displayed.

} } (document.images){ dcs_imgarray[dcs_ptr] = new Image; dcs_imgarray[dcs_ptr].src = dcs_src; WT[myMeta.name.substring(3)]=myMeta.content; } if DCSext[myMeta.name.substring(7)]=myMeta.content; } } } } for (N in DCS){P+=A( N, DCS[N]);} for (N in WT){P+=A( "WT."+N, WT[N]);} for (N in DCSext){P+=A( N, DCSext[N]);} //} aCrumb=aCookie[i].split("="); if (crumb==aCrumb[0]){ return aCrumb[1]; } } return null; } i=0;i