Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Administration   |   Topic List   |   Previous   |   Next   |   Contents

   Administering a BEA Tuxedo Application at Run Time

The procedure you follow to restore a failed machine depends on whether that machine was the MASTER machine.

To restore a failed MASTER machine, complete the following procedure.

1. Make sure that all IPC resources for the BEA Tuxedo processes that are removed.

2. Start a tmadmin session on the ACTING MASTER (SITE2).

   tmadmin

3. Boot the BBL on the MASTER (SITE1) by entering the following command.

   boot -B SITE1

   (The BBL does not boot if you have not executed pclean on SITE1.)

4. Still in tmadmin, start a DBBL running again on the MASTER site (SITE1) by entering the following.

   MASTER

5. If you have migrated application servers and data off the failed machine, boot them or migrate them back.

To restore a failed nonmaster machine, complete the following procedure.

1. On the MASTER machine, start a tmadmin session.

2. Run pclean, specifying the partitioned machine on the command line.

3. Fix the machine problem.

4. Restore the failed machine by booting the Bulletin Board Liaison (BBL) for the machine from the MASTER machine.

5. If you have migrated application servers and data from the failed machine, boot them or migrate them back.

In the following list, SITE2, a nonmaster machine, is restored.

$ tmadmin
tmadmin - Copyright © 1987-1990 AT&T; 1991-1993 USL. All rights reserved

> pclean SITE2
Cleaning the DBBL.

Pausing 10 seconds waiting for system to stabilize.
3 SITE2 servers removed from bulletin board

> boot -B SITE2
Booting admin processes ...

Exec BBL -A :

on SITE2 -> process id=22923 ... Started.
1 process started.
> q