General Upgrade Considerations

Preparing to Move from SLES 10 to SLES 11

Published
January 2016
Language
English (United States)
Last Update
2018-05-04
dita:mapPath
bdv1467307738050.ditamap
dita:ditavalPath
ft:empty
dita:id
yiu1467244923010
Product Category
Hardware
Software
The following considerations apply when transitioning from SLES 10 to SLES 11, regardless of platform and licensing.
  • If required as part of upgrading to SLES 11, perform hardware and Teradata Database upgrades well in advance. Doing so provides for monitoring the performance characteristics on the new database version so that you can better fine tune priority-scheduling settings prior to operating system upgrade.
  • You can upgrade to later Teradata Database versions one major release at a time until reaching the required version. In preparation for upgrading the database, be sure to review Teradata Database Node Software Upgrade Guide: Overview and Preparation.
  • If migrating between systems to upgrade the operating system, the Teradata Database version on the source system can be no more than two releases earlier than and cannot exceed the version installed on the destination system. In preparation for migrating a system, be sure to review Teradata Database Node Software Migration Guide for the applicable database version.
  • Backing up the TDWM database prior to upgrading the operating system ensures ongoing access to priority-scheduling configurations and functionality should you need to revert to the SLES 10 environment after completing the upgrade. In a migration scenario, the backup is restored on the destination system in preparation for the required workload conversion.
  • After upgrading to SLES 11, use the Workload Designer portlet in Teradata Viewpoint to review and adjust workload configurations as necessary.