SLES 10 to SLES 11 Upgrade Basics

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 path for transitioning from SLES 10 to SLES 11 depends on hardware.
  • If your existing hardware supports SLES 11, you can upgrade the operating system in place without migrating data.
  • If you have purchased different hardware that supports SLES 11, you must migrate data from your SLES 10 system to your SLES 11 system.

In either case, the required steps for transitioning a Teradata system vary depending on existing database and operating system versions.

Pre- and post-upgrade workload-management licensing, which may be dictated by existing hardware, also influence the following aspects of the upgrade:
  • Means of migrating workloads
  • Tasks to prepare workloads for migration
  • Workload-management options and required configuration post upgrade

Regardless of upgrade and workload-migration paths, transitioning from SLES 10 to SLES 11 has implications for workload priority scheduling in Teradata Database, because resource allocation is handled differently on the two operating systems. In addition, upgrading from SLES 10 to SLES 11 may result in CPU overhead of 6-8%.

Upgrading an operating system is an involved process that occurs in multiple phases beginning at least 90 days before and ending a day or two after the upgrade itself. To initiate the upgrade process, obtain a Change Control number from Teradata Customer Services.