A major or minor upgrade requires redeploying the system. For information on how to upgrade the Teradata Database running in a virtual or public cloud environment, log in to https://access.teradata.com and search for KCS001779.
| Upgrade Considerations | Requirements |
|---|---|
| Bundle Downloads | Download software upgrade bundles from the Teradata customer portal at https://access.teradata.com. |
| Operating System Updates | Because the operating system software bundle includes both important security updates and the latest version of the utility used to upgrade Teradata components (PUT), you must download this bundle whenever upgrading other Teradata components with the exception of Server Management, for which the required updates are included in the image itself. |
| Outage Preparation | When upgrading the operating system and Teradata components including Server Management, PUT does not set a maintenance window, but does automatically reboot the system. Plan accordingly. |
| Post-Upgrade Image Creation | You must create a new system image after a software upgrade. If you do not create this image, the software on the recovered instance will not match, and the database cannot start if a node failure occurs. |
| Stacks launched prior to Teradata Software for AWS 4.0 | If you are upgrading from an older Teradata Database version to Teradata Software for AWS 4.0 or later, additional permissions for rollback and scale out/in are required. Log in to https://access.teradata.com and search for KCS011002. No action is required for stacks launched with Teradata Software for AWS 4.0 and later as they have the proper permissions for rollback and scale out/in. |