...
| Anchor | ||||
|---|---|---|---|---|
|
Overview
In versions 7.5.x.x and earlier, all Universal Agent components (on Intel-based Solaris systems) were built on a 32-bit, little-endian Solaris Intel machine. With the release of 7.6.x.x, we have transitioned to a more robust 64-bit, little-endian Solaris Intel machine.
Implications of the Change
This transition, while offering numerous benefits, also means that the persistent data stored on disk by the components from previous releases is no longer compatible with the new release. Specifically, the binary format used for persistent data in earlier versions does not align with the new 64-bit architecture.
The following components are affected:
- OMS Server: creates message data files (in binary format) and persists them to disk to ensure message reliability. These files are not designed to be portable. See OMS Server Message Database.
- UAG: creates a job file (in binary format) for each task and persists it to disk until the task is completed.
Pre-Upgrade Steps
Before starting the pre-upgrade steps, ensure no tasks are being run involving the Solaris Intel machine being upgraded. This means there should not be any tasks in Queued or Running status. Any queued or running tasks will be lost.
- Suspend any Agents running on the Solaris Intel machine being upgraded.
- Suspend the OMS server running on the Solaris Intel machine being upgraded. This may not be necessary if the OMS server is on a different system.
- Stop the Universal Broker by running
/opt/universal/ubroker/ubrokerd stop - Delete any
.datafiles in/var/opt/universal/spool/oms - Delete any
_jobfiles in/var/opt/universal/uag/cache
Performing the Upgrade
After completing the abvoe pre-upgrade steps, you may proceed with the standard upgrade process detailed in the previous section. Upon successful upgrade, make sure to Resume the suspended Agent(s) and OMS server.
| Anchor | ||||
|---|---|---|---|---|
|
...