5.8.1 Pre-Upgrade Notes

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.