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

This topic provides instructions for troubleshooting a partition, identifying its cause, and taking action to recover from it. A network partition exists if one or more machines cannot access the MASTER machine. As the application administrator, you are responsible for detecting partitions and recovering from them.

A network partition may be caused by any the following failures:

• A network failure-either a transient failure, which corrects itself in minutes, or a severe failure, which requires you to take the partitioned machine out of the network

• A machine failure on either the MASTER machine or the nonmaster machine

• A BRIDGE failure

The procedure you follow to recover from a partitioned network depends on the cause of the partition.

You can detect a network partition in one of the following ways:

• Check the user log (ULOG) for messages that may shed light on the origin of the problem.

• Gather information about the network, server, and service, by running the tmadmin commands provided for this purpose.

How to Check the ULOG

When problems occur with the network, BEA Tuxedo system administrative servers start sending messages to the ULOG. If the ULOG is set up over a remote file system, all messages are written to the same log. In this scenario, you can run the tail(1) command on one file and check the failure messages displayed on the screen.

If, however, the remote file system is using the network in which the problem has occurred, the remote file system may no longer be available.

151804.gumby!DBBL.28446: ... : ERROR: BBL partitioned, machine=SITE2

The following is an example of a tmadmin session in which information is being collected about a partitioned network, a server, and a service on that network. Three tmadmin commands are run:

• pnw (the printnetwork command)

• psr (the printserver command)

• psc (the printservice command)

  Example tmadmin Session

  ---

  $ tmadmin
  > pnw SITE2
  Could not retrieve status from SITE2
  
  > psr -m SITE1
  a.out Name   Queue Name	   Grp Name   ID   Rq Done   Load Done   Current Service
  BBL          30002.00000  SITE1       0      -         -             ( - )
  DBBL         123456       SITE1	       0     121       6050          MASTERBB
  simpserv     00001.00001  GROUP1      	1	      -	         -	             ( - )
  BRIDGE	       16900672	     SITE1       	0      	-         	-	            ( DEAD )
  >psc -m SITE1
  Service Name Routine Name a.out    Grp Name ID Machine # Done Status
  ------------ ------------ -------- -------- -- ------- ------------ 
  ADJUNCTADMIN ADJUNCTADMIN BBL      SITE1     0   SITE1      - PART
  ADJUNCTBB    ADJUNCTBB    BBL      SITE1     0   SITE1      - PART
  TOUPPER      TOUPPER      simpserv GROUP1    1   SITE1      - PART
  BRIDGESVCNM  BRIDGESVCNM  BRIDGE   SITE1     1   SITE1      - PART

  ---

Restoring a Network Connection

This topic provides instructions for recovering from transient and severe network failures.

Because the BRIDGE tries, automatically, to recover from any transient network failures and reconnect, transient network failures are usually not noticed. If, however, you need to perform a manual recovery from a transient network failure, complete the following procedure.

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

2. Run the reconnect command (rco), specifying the names of nonpartitioned and partitioned machines.

   rco non-partioned_node1 partioned_node2

To recover from severe network failure, complete the following procedure.

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

2. Run the pclean command, specifying the name of the partitioned machine.

   pcl partioned_machine

3. Migrate the application servers or, once the problem has been corrected, reboot the machine.