When you migrate the MASTER to Oracle Tuxedo 22c Release 1 (22.1.0.0.0) (through a hot upgrade), you cannot migrate it back to the acting backup until you upgrade the backup to Oracle Tuxedo 22c Release 1 (22.1.0.0.0). Therefore, migrating the MASTER is irreversible; once the migration is complete, the MASTER cannot be reverted to its earlier Oracle Tuxedo release.

When you run tmadmin(1) on an Oracle Tuxedo 22c Release 1 (22.1.0.0.0) machine with a previous release MASTER, the UPGRADE file shown in Hot-Upgrade Example must reside in the current directory. To ensure that the files are in the current directory, you might, for example, run tmadmin from the Tuxedo application directory: $APPDIR (UNIX) directory.

Follow these guidelines when migrating Oracle Tuxedo data storage areas:

• You must remove the oldTUXCONFIG file. As TUXCONFIG is propagated automatically when the backup machine is run, no action is required on your part.
• Create the TLOG when you load the software. If you already have a TLOG, remove it.
• Do not do anything with application queue spaces and queues.
• If you have a Domains configuration (BDMCONFIG) file, leave it as is.

To minimize downtime, Oracle recommends installing Oracle Tuxedo 22c Release 1 (22.1.0.0.0) on the MASTER machine and backup MASTER, and rebuilding all clients and servers in the directory on each machine that is defined by $APPDIR, in parallel with the directory in which the old-release clients and servers were created. In other words, both an old-release application and an Oracle Tuxedo 22c Release 1 (22.1.0.0.0) application must be available on each machine. This advice is not a requirement, but a recommendation.

The Oracle Tuxedo software supports device list path entries of up to 256 bytes in length (in previous releases the limit was 64 bytes in length.) Queue Spaces, TLOG files, and other configuration files originally created with an earlier version of Oracle Tuxedo are understood and supported with this release. However, such device lists originally created with Oracle Tuxedo 8.0 or earlier are restricted to 64-byte path names. Therefore, if the administrator wants to add a new extent using a path name greater than 64 bytes in length to a queue space in the future and such queue space is empty when the upgrade is performed, the administrator may want to create the queue space device list and the queue space at the time of the hot upgrade. Many applications need to preserve queue spaces across an upgrade, and do not to recreate them. Furthermore, most applications do not need to add queue space extent in the future or are able to do so using path names no longer than the ones they are currently using. This queue space recreation is completely optional and mentioned for completeness.

If you already have DMTLOG and TLOG, make sure that no pending transaction logs are in them before shutting down the application. In addition, ensure that you remove the DMTLOG and TLOG (if they exist) after the application is shut down.

This section provides an overview of the tasks for a “hot upgrade.”

1. Ensure your environment is set up as follows:
   • The configuration must have a backup MASTER machine.
   • The MODEL option in the configuration must be set to MP.
   • The MIGRATE option in the configuration must be set.
2. If upgrading an Oracle Tuxedo 9.1 machine, uninstall the Oracle Tuxedo system software as specified in Uninstalling Oracle Tuxedo.
3. Shut down the backup MASTER machine.
4. Install the Oracle Tuxedo 22c Release 1 (22.1.0.0.0) software on the backup MASTER machine and reboot the backup machine.
5. Migrate the MASTER machine running the old release to the backup MASTER machine running Oracle Tuxedo 22c Release 1 (22.1.0.0.0).
6. Shut down the machine that is now acting as the backup MASTER.
7. Install Oracle Tuxedo 22c Release 1 (22.1.0.0.0) on the old MASTER.
8. Using Oracle Tuxedo 22c Release 1 (22.1.0.0.0), reboot the machine that you shut down in step 7.

For more information about hot upgrades, see Hot-Upgrade Example.

The following example describes a sample scenario for a hot upgrade and the sequence of steps to perform the hot upgrade.

The following example describes an example scenario for a hot upgrade and the sequence of steps to perform the hot upgrade:

1. Ensure that your environment has been set up as follows (for MP mode, you must configure the UBBCONFIG file in the $APPDIR of the MASTER machine).
   1. Refer to the ubbmp file of the sample bank application for reference.
   2. In the resource section of the configuration, the BACKUP MASTER machine must be specified. Follow the steps below:
      • Under the *RESOURCES section, select the value of MASTER as MACH1, MACH2 (where, MACH2 is the backup master machine), the following is the example:

        MASTER      MACH1,MACH2

   3. In the configuration, the MODEL option must be set to MP under the *RESOURCES section.
   4. In the configuration, the MIGRATE option must be set.

      OPTIONS         LAN, MIGRATE

   5. Ensure that the Network section is configured with both NADDR and NLSADDR (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>"

   6. Both the MASTER and BACKUP MASTER machines must be installed with the old Tuxedo version.
   7. Start Tlisten on both the MASTER and BACKUP MASTER machines. In the section of UBBCONFIG Network, you must specify the same address as NLSADDR for the tlisten.
   8. Follow the README of the sample application to generate the server and client files, in this case "simpserv" and "simpcl".
2. Run the Tmboot command on MACH1 after generating the tmconfig file from the above configuration file.

    MACH1> tmloadcf -y ubbmp

3. The Tmboot on Machine1 (MASTER machine) generates a tmconfig on the BACKUP MASTER machine (MACH2)
4. Use the following command to shut down the backup MASTER machine from MACH1:

   MACH1> tmshutdown -B MACH2 -l MACH2

5. Use the following command to kill the tlisten process on the backup master machine (MACH2)  

   ps -ef | grep tlisten 

   kill -9 <pid of the tlisten got from above command>

6. Install the Oracle Tuxedo 22c Release 1 (22.1.0.0.0) software on the backup MASTER machine.
7. Cd  $Appdir of MACH2 and rm tuxconfig file.
8. Prior to running tmconfig to update the APPDIR, TUXCONFIG, and TUXDIR for MACH2 on the UBBCONFIG file available in the MACH1, export EDITOR=vi to enable editing in the vi editor:

   MACH1> tmconfig
   choose option 2)MACHINES
   choose option 5)Update

   TA_LMID<the machine LMID for which you want an update> (You can find the value of LMID in UBBCONFIG file *MACHINES section)

   TA_APPDIR Value of the new appdir
   TA_TUXDIR Value of new tuxdir
   TA_TUXCONFIG value of new TUXCONFIG

   TA_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 Y for the confirmation. For more information about tmconfig, see How to Run tmconfig.
   • Run tmunloadcf to verify successful update.
9. To set PATH, LD_LIBRARY, and TUXDIR to the latest release of Tuxedo, run tux.env from the newly installed Tuxedo product in MACH2.
10. Ensure TUXCONFIG and APPDIR point to the latest version of Tuxedo.
11. Use the following command to create a file UPGRADE inside the $APPDIR of MACH2

    touch UPGRADE

12. 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

13. Start the Oracle Tuxedo 22c Release 1 (22.1.0.0.0) tlisten in MACH2.
14. Reboot the backup MASTER machine using the following command from MACH1:

    MACH1> tmboot -B MACH2 -l MACH2 

    verify the tmconfig file generated in this process is located in $APPDIR

15. Migrate the MASTER machine running the old release to the MASTER machine running the latest release.

    After running the MASTER command, you must not encounter any errors and PSR displays the services running on the machine.

    MACH2> tmadmin
                   master
                   y
                   psr
                   q

16. Use the following command to kill the tlisten from MACH1:

    ps -ef | grep tlisten
    kill -9 <pid of the tlisten got from above command>

17. Ensure that Oracle Tuxedo 22c Release 1 (22.1.0.0.0) software is installed on the OLD MASTER machine (MACH1).
18. Delete the tuxconfig file from $APPDIR of the MACH1 (if it exists).
19. Run tmconfig file on the MACH 2 to reset the APPDIR, TUXCONFIG, and TUXDIR for MACH1 on the UBBCONFIG file, and then export EDITOR=vi before running tmconfig file to enable the modification to be completed with the vi editor:

    • MACH2> tmconfig
      choose option 2)MACHINES 
      choose option 5)Update

      Pass 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 Y for the confirmation. For more information about tmconfig, see How to Run tmconfig.
    • Run tmunloadcf to verify successful update.
20. Set the PATH, LD_LIBRARY, and TUXDIR to the latest release of Tuxedo in MACH1 by running the tux.env file from the newly installed Tuxedo product.
21. Ensure TUXCONFIG and APPDIR point to the latest version of Tuxedo.
22. 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

23. Start the Oracle Tuxedo 22c tlisten in MACH1.
24. Using the following command to reboot the OLD MASTER machine (MACH1) from the MACH2:

    MACH2> tmboot -B MACH1 -l MACH1 

    Verify tmconfig is generated in $APPDIR in this process.

25. Delete the UPGRADE command from MACHINE2 $APPDIR

Some Oracle Tuxedo functions are delivered in object files in the Oracle Tuxedo release 12.1.3 (or lower). In this Oracle Tuxedo release, these object files are packaged in libraries. When rebuilding the corresponding executables, you need to link with the related libraries instead of the object files as listed in the following table: