5.8.3 Hot-Upgrade Example
The following example describes a sample scenario for a hot upgrade and the sequence of steps to perform the hot upgrade.
Suppose you have the following on a UNIX platform:
- A machine called
MACH1that is configured as theMASTERand that runs an old release.- A corresponding application directory called
$APPDIR1 - A corresponding configuration file called
$TUXCONFIG1
- A corresponding application directory called
- A machine called
MACH2that is configured as the backup.- A corresponding application directory called
$APPDIR2 - A corresponding configuration file called
$TUXCONFIG2
- A corresponding application directory called
The following example describes an example scenario for a hot upgrade and the sequence of steps to perform the hot upgrade:
- Ensure that your environment has been set up as follows (for
MPmode, you must configure theUBBCONFIGfile in the$APPDIRof theMASTERmachine).- Refer to the
ubbmpfile of the sample bank application for reference. - In the resource section of the configuration, the
BACKUP MASTERmachine must be specified. Follow the steps below:- Under the
*RESOURCESsection, select the value ofMASTERasMACH1,MACH2(where,MACH2is the backup master machine), the following is the example:MASTER MACH1,MACH2
- Under the
- In the configuration, the
MODELoption must be set toMPunder the*RESOURCESsection. - In the configuration, the
MIGRATEoption must be set.OPTIONS LAN, MIGRATE - Ensure that the Network section is configured with both
NADDRandNLSADDR(both must be on separate ports).*NETWORK MACH1 NADDR="//<MACH1_Hostname>:<naddr_port_number>" #BRIDGE="/scratch/<user_name>" NLSADDR="//<MACH1_Hostname>:<nls_port_number>" MACH2 NADDR="//<MACH2_Hostname>:<naddr_port_number>" #BRIDGE="/scratch/user_name" NLSADDR="//<MACH2_Hostname>:<nls_port_number>" - Both the
MASTERandBACKUP MASTERmachines must be installed with the old Tuxedo version. - Start
Tlistenon both theMASTERandBACKUP MASTERmachines. In the section ofUBBCONFIGNetwork, you must specify the same address asNLSADDRfor thetlisten. - Follow the
READMEof the sample application to generate the server and client files, in this case "simpserv" and "simpcl".
- Refer to the
- Run the
Tmbootcommand onMACH1after generating thetmconfigfile from the above configuration file.MACH1> tmloadcf -y ubbmp - The
Tmbooton Machine1 (MASTERmachine) generates atmconfigon theBACKUP MASTERmachine (MACH2) - Use the following command to shut down the backup
MASTERmachine fromMACH1:MACH1> tmshutdown -B MACH2 -l MACH2 - Use the following command to kill the
tlistenprocess on the backup master machine (MACH2)ps -ef | grep tlistenkill -9 <pid of the tlisten got from above command> - Install the Oracle Tuxedo 22c Release 1 (22.1.0.0.0) software on the backup
MASTERmachine. Cd $AppdirofMACH2andrm tuxconfigfile.- Prior to running
tmconfigto update theAPPDIR,TUXCONFIG, andTUXDIRforMACH2on theUBBCONFIGfile available in theMACH1, exportEDITOR=vito enable editing in the vi editor:MACH1> tmconfig choose option 2)MACHINES choose option 5)UpdateTA_LMID<the machine LMID for which you want an update>(You can find the value ofLMIDin UBBCONFIG file*MACHINESsection)TA_APPDIR Value of the new appdir TA_TUXDIR Value of new tuxdir TA_TUXCONFIG value of new TUXCONFIGTA_LMID MACH2 TA_APPDIR /scratch/<user_name>/oraHome_22c_load11/tuxedo22.1.0.0.0/samples/atmi/simpapp TA_APPDIR /scratch/<user_name>/oraHome_22c_load11/tuxedo22.1.0.0.0 TA_APPDIR /scratch/<user_name>/oraHome_22c_load11/tuxedo22.1.0.0.0/samples/atmi/tuxconfig- Run the command
wq!to save and exit - Select
Yfor the confirmation. For more information abouttmconfig, see How to Run tmconfig. - Run
tmunloadcfto verify successful update.
- Run the command
- To set
PATH, LD_LIBRARY, andTUXDIRto the latest release of Tuxedo, runtux.envfrom the newly installed Tuxedo product inMACH2. - Ensure
TUXCONFIGandAPPDIRpoint to the latest version of Tuxedo. - Use the following command to create a file
UPGRADEinside the$APPDIRofMACH2touch UPGRADE - In
MACH2, export the following Security environment variables:export LLE_DEPRECATION_WARN_LEVEL=NONE export TM_USE_OLD_CIPHER=Y export TM_ALLOW_NOTLS=Y export TM_MIN_PUB_KEY_LENGTH=0 export TM_SECURITY_CONFIG=NONE - Start the Oracle Tuxedo 22c Release 1 (22.1.0.0.0)
tlisteninMACH2. - Reboot the backup
MASTERmachine using the following command fromMACH1:MACH1> tmboot -B MACH2 -l MACH2verify the tmconfig file generated in this process is located in $APPDIR - Migrate the
MASTERmachine running the old release to theMASTERmachine running the latest release.After running the
MASTERcommand, you must not encounter any errors and PSR displays the services running on the machine.MACH2> tmadmin master y psr q - Use the following command to kill the
tlistenfromMACH1:ps -ef | grep tlisten kill -9 <pid of the tlisten got from above command> - Ensure that Oracle Tuxedo 22c Release 1 (22.1.0.0.0) software is installed on the OLD
MASTERmachine (MACH1). - Delete the
tuxconfigfile from $APPDIRof theMACH1(if it exists). - Run
tmconfigfile on theMACH 2to reset theAPPDIR,TUXCONFIG, andTUXDIRforMACH1on theUBBCONFIGfile, and then exportEDITOR=vibefore runningtmconfigfile to enable the modification to be completed with the vi editor:MACH2> tmconfig choose option 2)MACHINES choose option 5)UpdatePass the following variables in key-value pairs with tab to update the details of a specific machine.
TA_LMID MACH1 TA_APPDIR Value of the new appdir TA_TUXDIR Value of new tuxdir TA_TUXCONFIG value of new TUXCONFIG- Run the command
wq!to save and exit. - Select
Yfor the confirmation. For more information abouttmconfig, see How to Run tmconfig. - Run
tmunloadcfto verify successful update.
- Set the
PATH, LD_LIBRARY, andTUXDIRto the latest release of Tuxedo inMACH1by running thetux.envfile from the newly installed Tuxedo product. - Ensure
TUXCONFIGandAPPDIRpoint to the latest version of Tuxedo. - Export the following environment variables in
MACH1:MACH1> export LLE_DEPRECATION_WARN_LEVEL=NONE export TM_USE_OLD_CIPHER=Y export TM_ALLOW_NOTLS=Y export TM_MIN_PUB_KEY_LENGTH=0 export TM_SECURITY_CONFIG=NONE - Start the Oracle Tuxedo 22c tlisten in
MACH1. - Using the following command to reboot the OLD
MASTERmachine(MACH1)from theMACH2:MACH2> tmboot -B MACH1 -l MACH1Verify tmconfig is generated in $APPDIR in this process. - Delete the
UPGRADEcommand fromMACHINE2$APPDIR
Parent topic: Performing a Hot Upgrade