Customer Best Practices for Teradata Software Upgrades

Customer Best Practices for Teradata Upgrades

Major Software Upgrades

Partners Service Focus Team


Customer Best Practices for Teradata Software Upgrades

Revision History
Summary of Changes Date
June 23/08 July !" 2008 July 1'" 2008 July 12"2008 Septem er )/2008 +e(em er 3" 2012

Description of Change
Initial input from all areas First inte#rate$ $raft Se(on$ inte#rate$ $raft T&ir$ Inte#rate$ $raft Fourt& Inte#rate$ $raft ,p$ates to refle(t (urrent pro$u(ts - versions

0.1 0.2 0.3 0.) 0.! 1.0

SFT Mem ers %eit& Jones %eit& Jones S&elley *errior S&elley *errior Jerry .levins

!mportant "otes Date
July !" 2008 T&is initial version of t&e $o(ument /as /ritten /&ile Tera$ata 02R1.2 /as /i$ely a((epte$ as t&e (urrent sta le version" an$ 012 /as startin# to e a$opte$ y (ustomers. 2ny instru(tions an$ soft/are referen(es in t&is $o(ument s&oul$ e ta3en /it& t&at (onte4t in min$. T&is up$ate$ version of t&e $o(ument /as /ritten /&ile Tera$ata T+13 /as /i$ely a((epte$ as t&e (urrent sta le version" an$ T+1) /as startin# to e a$opte$ y (ustomers. 2ny instru(tions an$ soft/are referen(es in t&is $o(ument s&oul$ e ta3en /it& t&at (onte4t in min$.

2u#ust 21" 2012

Partners Service Focus Team


.................................................... '......... ' Re#ression Testin#.............. %*& C$osing&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& %- Partners Service Focus Team iii .......................... 1... 1 *re7up#ra$e ................& Upgrade Teradata Too$s and Uti$ities&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&%' /& Upgrade Teradata Managed Server pp$ications&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&%' %+& Upgrade B R Software&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&%( %%& Teradata Pre0Upgrade Preparations&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&%) %'& Teradata Upgrade&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& %* %(& Post0Upgrade Steps&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& %* %)& Project C$oseout&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& %....................p#ra$es" +efine$................... ............. Ma5or +ata ase Soft/are .................... Resear(& t&e ne/ version.................... ' %ey Ris3 8uestions to e ans/ere$..............................................................Customer Best Practices for Teradata Software Upgrades Ta#$e of Contents %& !ntroduction&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& % '& The Upgrade Process for Teradata Software&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&( 1...............p#ra$e *ro(ess 6vervie/ +ia#ram......................................................................................................................................................................3 2.................. 3 (& Project Management&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& ) )& Upgrade P$anning&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&* 3................. )................................................................... ! I$entify your $epen$ent appli(ations.......................................................................en(&mar3in#............................... ' *& User Communication&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& %+ ........................... !.....& Change Contro$&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& %% -& Upgrade C$ient Software&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&%' .......

but are not limited to: • • • • • • • !lanning "oordination "ommunication Testing #enchmar$ing %xecution !ro&ect management 'pgrades can include database software (ma&or. *ardware upgrades and expansions are covered in a separate document which can be found here. but assumed to be present and bear no negative impact on the upgrade process. migration). maintenance) and database hardware (upgrade. It is /ritten y (ustomers9 for use y (ustomers.ervice ocusTeam/-hitepapers Note to the reader. there are three things that influence the success or failure of an upgrade: • • • The quality of the product being added/upgraded The service procedures followed by Teradata associates The planning and execution of operational procedures by the customer All three need to come together without flaw during the upgrade process in order to achieve success. They are accurate to the "est com"ined $now!edge of the team% "ut shou!d a!ways "e fo!!owed with caution and good &udgment as they are not guaranteed to "e free from f!aws. A successful upgrade of any computing environment requires careful planning. This white paper will focus only on database software upgrades. The success you experience is in part dependent on the success of your efforts throughout the process. they are considered out of scope. In general. Partners Service Focus Team ' . The procedures are meant to "e high !eve! guides and do not represent step#"y#step procedures. The procedures represent the com"ined !earning of the customer mem"ers who contri"uted to it.teradata+partners. minor. It comes as is with no imp!ied support. expansion. or the purposes of this paper. They include. http://www. and execution. This paper will focus on those operational procedures which are the responsibility of the customer. The first two are the responsibility of Teradata. This guide is provided as a courtesy of the Teradata Partners Service Focus Team (SFT).com/About/. coordination.Customer Best Practices for Teradata Software Upgrades %& !ntroduction T&is paper is prepare$ for t&e use an$ enefit of Tera$ata (ustomers. There are many factors that need to be considered and brought together for a successful plan. A Teradata computing environment is no different.

Customer Best Practices for Teradata Software Upgrades Partners Service Focus Team ( .

Upgrade Process 2verview Diagram This diagram gives an overview of the upgrade process. 0oving from Teradata 12 to Teradata 13 is a ma&or upgrade. A ma&or database software upgrade is moving from one database version to another as represented by the following software version numbering format: a. The body of this document will describe each tas$ in more detail: Partners Service Focus Team ) .ccc.a/ being a ma&or release of the database. as well as some Requests for Change (RFCs and Discre!ancy Re!orts (DRs . user data or custom user features. user data or custom user features. many of the points in this document could apply to minor software upgrades as well. *owever.Customer Best Practices for Teradata Software Upgrades '& The Upgrade Process for Teradata Software Major Data#ase Software Upgrades1 Defined This paper deals primarily with ma&or database software upgrades. A minor u!grade generally does not include the conversion of system tables. with . A Teradata Database major release generally includes significant new features and enhancements which may involve the conversion of system tables. A Teradata Database minor release may include a number of new features and

operations.6) in the team meetings. This person will ensure that all involved parties communicate effectively.p#ra$e *lannin# .Customer Best Practices for Teradata Software Upgrades .p#ra$e :lient Soft/are .2R Soft/are Tera$ata *re7. *ave a $ic$+off meeting to update everyone and then provide regular status updates to the members.p#ra$e Steps *ro5e(t :loseout 3igure %4 Upgrade Process 2verview Diagram (& Project Management Any successful pro&ect requires strong and focused pro&ect management.p#ra$e *rep Tera$ata . Assign a pro&ect manager to coordinate all the required tas$s as a single pro&ect. developers.ser :ommuni(ation :&an#e :ontrol *ro5e(t Mana#ement .p#ra$e . performance / testing specialists and others to ensure cross+team participation and communication. and all tas$s are completed successfully. A Teradata upgrade is a significant underta$ing that is well worth treating as a formal pro&ect. "reate an upgrade team with 4#As. schedules are set and followed.ervice 6epresentative (". Partners Service Focus Team * .p#ra$e *ost7. 5ou may want to include your Teradata "ustomer .

These can be • • Partners Service Focus Team + . Teradata provides scripts to chec$ existing database ob&ects for use of reserved words. obtain I! addresses. Ta$e the time up front to investigate the new version before ta$ing the plunge. o 4uring the upgrade give timely (maybe every 3 hours) updates on the upgrade progress. and the 46s in the second pac$age but not the first. The time invested upfront will pay off later. This will help you identify any necessary changes to existing application . "ommunication could ma$e or brea$ the pro&ect. !ac$age "omparison Tool. o A . whereas others will need the very latest information during the actual upgrade. There are usually significant changes and improvements between ma&or versions. Are you prepared to accept non+supported configurations9 or example. #e sure to $now who will test changes and be sure that they have a proper test plan. http://www. T member 4#As have found it helpful to maintain an upgrade plan template document that covers both hardware and software changes. 8ther points to be considered as part of your pro&ect plan include: • "onsider what progress needs to be communicated to whom and at what points. it=s a great place to sociali>e with your peers and build helpful relationships. These are available around the world and are usually held twice a year.Tools and 6eports/ menu. or example. !laces to find information are: • • !artners !resentations.Customer Best Practices for Teradata Software Upgrades . In addition to hearing presentation material. -ill your own staff carry out the changes and execution of the testing (performance) plan9 -ill Teradata employees ma$e any of the changes9 -ill other 2 rd party employees ma$e the changes9 *ave you developed a 6is$ 0anagement !lan9 -hat are the alternative courses of action9 o o o o o o )& Upgrade P$anning An upgrade can be complex. 4oes your site have software distribution mechanisms li$e pac$ages for des$tops and servers9 If not. put in place processes to ensure that the change ta$es place in the same way for each similar change.teradata+partners. this report displays the 46s (4iscrepancy 6eports) in the first pac$age but not the second. ma$e 47. when adding new nodes you would want to remember to request firewall rules changes. Attendance is free of charge. can you obtain approval for running a non+ supported configuration9 -ho from your company will approve the configuration9 Agree well ahead of time who will wor$ on the pro&ect and obtain commitment that they will be available.ervice website under the . *owever. Research the new version ind the differences between the new version and your current version. This is available on the Teradata At 5our . Attend a local Teradata 'ser <roup meeting. This is a living document to which you would add new reminders learned during each new upgrade. these scripts donAt identify usage as aliases in the user queries.ome .teradata.teering "ommittee may need a monthly report.?@. 6eserved -ords 4ocument. It lists items to remember for specific circumstances. :arious presentations exist describing the new version and its features which are available via the !artners website to attendees of the conference for up to . entries. <iven two pac$age version numbers. etc. This $nowledge is invaluable in determining your particular ris$s and benefits of upgrading to a particular new version. if you are not able to upgrade exploitation tools before a database software upgrade.

?@ undamentals Appendix % (. be upgraded prior to the database server 8/. .ervers (:iewpoint. 4ata 0over. 4"0. "hec$ for changes to 4#?@. 7ote. Investigate changes to 4#?@ and 6esusage tables.teradata. non+production. 7ew version manuals.?@ eature summary) will detail . !dentify your dependent app$ications #e sure you $now all the Teradata client applications in use and investigate whether they are able to use the new Teradata version. upgrades occur9 4o they have to be done at the same time or could the #A6 server 8/. and prepare changes to your &obs that move such data into your history tables.ome Teradata and/or third+party applications using Teradata will need to be upgraded in order to wor$ with the new 6eference applicable 8range #oo$s available via TC5.ome potential clients include: • • • • • • • • Third+party reporting tools such as 0icrostrategy."87T68@ parameters + as$ Teradata to provide recommended values for them. .) .ee following section for details). <olden <ate) 4#A house$eeping scripts that are dependent on the data dictionary (4#") schema. Third+party %T@ tools li$e ab initio and Informatica. http://developer.A. "ognos. or critical applications. 5our data will need to be bac$ed up and then restored after the upgrade. If you are planning an 8/. upgrade as part of the pro&ect. but still gives you a chance to try the latest feature functionality. Investigate new 4#. These are available on "4 and on the Teradata website at http://www. %tc) Teradata Tools and 'tilities (TT') client software (. resusage and ad&ust 4#A scripts accordingly. (Note: if you are not logging SQL text in DBQL you really should be. specifically the 6elease definition and 6elease . In what order should the 8/.Customer Best Practices for Teradata Software Upgrades • • • • • • • • found by querying the 4#?@ sections D E 1F 6eplication solutions ( 'nity. Teradata #ac$up and 6ecovery (#A6) software (. 6esearch 4evB with an upgrade tag. it may be necessary to delay the Teradata upgrade until a compatible version is available. .ee following section for details). 8nce they are upgraded they will need to be tested. This could be a great way to get your hands on the new version prior to purchasing it.?@ differences.teradata.9 Partners Service Focus Team . Are there pre+requisites that affect the order of changes9 An obvious one is that TT' software would normally be upgraded ahead of database software. non+supported :irtual 0achine. http://developer. Teradata Applications (A60. and #usiness 8b&ects. Teradata 0anaged . T0.0.ummaries for the new version. you will be executing a migration which will require an extra level of planning with Teradata. to set your expectations properly as a :0 running on your !" will have poor performance. and discuss values with your local Teradata team "hec$ to see if the version you want to upgrade to is available as a downloadable. 5ou may also want to consider becoming involved in an % T (%ngineering ield Trial) or #%TA testing program for the new version. 'nity) . .teradata.

or more detailed information regarding #enchmar$ing practices please refer to the . "reating a scenario to test this will help to prevent surprises after an upgrade. Upgrade Risk Item Statistics Collection Description There are often questions as to whether statistics need to be collected before or after an upgrade. put focus on mission critical tables for statistics recollection during Partners Service Focus Team - . 5ou will want to ensure that the various wor$loads will continue to perform as expected when the system is saturated. T. you=ll want to identify queries you can use for before/after benchmar$ing. #e sure you have a bac$up of 4#?@ or whatever table you use to store this information so you are sure to have it after the upgrade.?@ and possibly some more complex queries that may have caused problems in the past. Types of .Customer Best Practices for Teradata Software Upgrades Pre0upgrade Benchmar5ing If your management is concerned about the 6eturn on Investment (68I) of the upgrade. astexport. Teradata always • Mitigation Steps Develop a plan to focus on stats recollection during the outage window for mission critical tables. archive and restore &obs in your benchmar$ suite.docx Regression Testing -e strongly advise that you install the new Teradata version on a test system first and then perform some regression testing. frequently run queries. 'se the T. TH#enchmar$ingHv. 4#?@ is a great resource to capture this information."ontent/docs/. T "ustomer #est !ractices for Teradata #enchmar$ing whitepaper available at http://www.1 inal. astload. 7ote that run+time should be long enough to retrieve comparable runtime figures. The customer needs to identify what tables are deemed mission critical. there will always be ris$s that need to be mitigated prior to execution of the upgrade. run the queries when the system is quiet before and after the upgrade to accurately compare results. 5ou may want to include T!T. Geep in mind they might run faster than usual on a quiet system. elapsed times and details for each query. #e sure to include queries from your most critical applications. Another important area you may need to consider is performance if you have a mixed wor$load. T+!ump. If you can=t copy down production data to test with.F different queries.?@ you may want to include are expedited queries. This will ensure that you get the same explains in test that you=ll get in production. heavy hitting queries. 6ey Ris5 7uestions to #e answered -henever you underta$e a ma&or software upgrade.%T utility to replicate your production test bed including statistics to the test system.teradata+partners.%T information. %T@ . "ollect explain output. The benchmar$ queries mentioned above would be good contenders for the testing. If possible.. -e recommend you identify at least 1F+. The following table provides a list of some common ris$ items and mitigation steps that can be ta$en to reduce or prevent any business impact associated with the ris$. at least run explains on your critical queries to chec$ for syntax errors and parser problems li$e segment violations (2I1F errors). canary queries. Teradata Guidance • Assuming there isn’t enough time to recollect all statistics. using a tiered approach.

Teradata Guidance • outage window.plains+ o /ulti Column stats %!igh Confidence in e. #lan for isolated statistics refresh given une. !owever. • Mitigation Steps #riority for what stats are collected on a given table should be in the following order$ o #artition Stats %on system defined columns #A&T'T'() on both ##' and non*##' tables+ .pected performance issues.pansion+ o Single Columns stats %!igh Confidence in e. or during their ne. statistics collection can ta"e some time. this is mandatory o #' and )-S' stats %)-S' stats should always be recollected after a system e.plains+ o Single Column stats and /ulti column stats %both with low Confidence+ Consider freshness of statistics as you develop your plan %i. and it may not always be feasible to do a full statistics collection during an upgrade window. and have e. when the last time statistics were collected on a given table+. &ecollect statistics that are "nown to be stale. &ecollect all #artition and )-S' statistics on the system. #hase in remaining statistics either on a best effort basis during non* business impacting hours. .ceeded their normal re*collection time.e.t scheduled refresh. • • • • Partners Service Focus Team .Customer Best Practices for Teradata Software Upgrades Upgrade Risk Item Description recommends having fresh statistics for the best optimi er performance.

this would have to be an agreed upon between Teradata and customer. or other web* based connectivity option that allows for sharing des"tops as a bac"up method for connecting to the Teradata systems from a customer des"top. Service Connect %A. as well as scandis" • • • 7.ecuted another chec"table level 6 2ust prior to the system outage window and address any remaining issues. The failure of 8#) connectivity can compromise what can be done. 7. this is least desirable. 7. and add significant ris" to getting all upgrade wor" completed. 'f present. #lan for and pre*test 3eb7. determine ahead of time what can be done to pre*test or mitigate any e. The chec" table pending ops can ta"e much longer to run on larger systems with many ob2ects.posure during the software upgrade. 8#). and is a standard utility to determine if issues e. This should be tested in advance of the upgrade.ecute chec"table level 6 on dbc. successfully dealing with identified ob2ects may e. • • • Assume normal 8#) connectivity in the plan. or other web* based des"top sharing solution to be used as bac"up Consider having local CS& support during the software upgrade that can be onsite in the data center if the first two options do not wor" . Partners Service Focus Team / . level 4 on other tables post merge. • • 7. 7.ecute chec"table 0 pending ops level at beginning of outage window .ecute as an upgrade prep process.ecute on a system. 3hile the utility typically ta"es 45* 65 minutes to e. The typical way is through a 8#) connection that is already in place for normal customer support with any ob2ects that must be addressed prior to an upgrade process commencing. 3hile an option. leverage onsite Teradata CS& resources to assist in the completion of all required activities.ecute multiple chec"table level 6 operations as part of normal planning to ensure that issues are resolved well ahead of time. 7.tend the time required in the plan.ternal )etwor" Connectivity #roblems • • • -nderstand from customer if there is scheduled networ" maintenance or other activities that would potentially impact Teradata 8#) system connectivity. -se 3eb7.Customer Best Practices for Teradata Software Upgrades Chec" Table 0 #ending (ps 1evel during system outage window This is designed to e. there should be no significant errors.eda+.ecute chec"table level 6 during normal prep activities and successfully resolve any identified issues. Teradata Customer Services will most li"ely need to access your systems remotely during the software upgrade. which could add time to the outage window. As a third option.

This provides the customer with fle. but always a good thing to do. 7. o 3or"s with system>site CS& personnel to communicate issues that require additional attention or follow*up. *& User Communication 5ou will want to $eep your users well+informed regarding the upgrade timing and with each other. wee"s out from e. and build out 2oint detailed run boo". "onsider giving a new features overview class. • • • • #rovide ample time and appropriate software upgrade windows for Teradata Customer Services team to complete all activities. Partners Service Focus Team '0 . This service is conducted within = days from the software upgrade event and includes wor" performed by the CS organi ation$ o Accesses the system and performs the data collection process. 6equest users to drop unneeded ob&ects from their personal databases. but it is important that appropriate planning steps are conducted in advance to ensure a successful software upgrade.pansion window to develop detailed run boo" with multiple wal"* throughs between Teradata and the customers D<A team. • • • 7nsure that all required prep windows are obtained prior to the software upgrade.ecute new Teradata Customer Services #re*-pgrade Assessment Service.ecute recommended pre* upgrade activities performed by both Teradata #rofessional Services personnel and Teradata Customer Services personnel. Ideas for user communications include: • • • • !ass on your findings on the use of new reserved words in existing user . o Analy es data to pinpoint "nown performance opportunities. &un #DC& data collection reports to be reviewed by the Teradata Customer Services for identification of any issues. o Completes Assessment and delivers to the system>site CS&s and SS/ for review. o Data Collection process is non*intrusive and will not impact the system.Customer Best Practices for Teradata Software Upgrades 9eneral ris"s The Teradata database supports investment protection through its ability to support multiple generations of Teradata platform hardware. !ublish upgrade information and schedule on your intranet website.?@.ibility. /eet twice per wee" :*. including the ability to have nodes of different generations co* e. Conduct bi*wee"ly status meetings to develop and review plan. 7. This is more important for hardware upgrades.

. functional testing. . o 4uring the upgrade give timely (maybe every 3 hours) updates on the upgrade progress. %nsure that you have developed a proper test plan (connectivity testing. volume testing. Include any data load tools being upgraded as well.Customer Best Practices for Teradata Software Upgrades • • • :erify with users that all their critical data will be bac$ed up. #usiness 8b&ects and "ognos. performance testing specialists early in the process. Partners Service Focus Team '' . %nsure that you ta$e into account the lead time required for the Teradata "hange "ontrol process. "onsider if you want to include Teradata !. Are you prepared to accept non+supported configurations9 or example. %xecute a pilot rollout of TT' to ensure a smooth upgrade. 0any of the points included in your change control procedures should also be considered as part of your upgrade planning process. o A . performance testing. .& Change Contro$ The argument for formal change control is that system upgrades are managed in a controlled and successful manner such that there is minimal negative impact on the users of the system. 0ain points to consider and potentially include in your change control procedures are: • • • • • • • • • • Include all software that is being touched. 4oes your site have software distribution mechanisms li$e pac$ages for des$tops and servers9 If not. "hange control helps ensure all eventualities have been considered and communicated.A.teering "ommittee may need a monthly report. user acceptance testing) and that you $now who will execute the testing. can you obtain approval for running a non+supported configuration9 -ho from your company will approve the configuration9 Agree well ahead of time who will wor$ on the pro&ect and obtain commitment that they will be available. Are there pre+requisites that affect the order of changes9 An obvious one is that TT' software would normally be upgraded ahead of database software. #e very clear about when changes are to ta$e place and how long they are expected to ta$e. -ill your own staff carry out the changes9 -ill Teradata employees ma$e any of the changes9 -ill other 2rd party employees ma$e the changes9 All changes must have a bac$out mechanism. • • The $ey to successful change is planning and communication. "onsider what progress needs to be communicated to whom and at what points. put in place processes to ensure that the change ta$es place in the same way for each similar change.g. data integrity testing. you need to include all data exploitation tools being upgraded as well. e. if you don=t already regularly bac$ up user personal databases. Apart from the obvious new Teradata database release and its client software. whereas others will need the very latest information during the actual upgrade. "ommunication could ma$e or brea$ the pro&ect. 0a$e sure your change control includes a list of contact names and details for use during the time of change. 6emember to test that mechanism where possible. !rovide a demo of new tools available in the new release. if you are not able to upgrade exploitation tools before a database software upgrade.

#e sure to do regression testing of unique features of your environment.pecifics on that are outside the scope of this document. "reate an implementation plan and chec$list to ensure none are missed. 'ninstall the old version prior to installing the new one. 8.g. Partners Service Focus Team '( . Teradata Administrator (-in44I) and #T%? are the most commonly used components. . %nsure this TT' version will wor$ with the database version. -or$ with your third+party software vendors to upgrade their products according to their recommendations. uture TT' versions will be forward compatible with the next database release.TT'/ refers to the Teradata+supplied Tools and 'tilities that enable a client to interface with a Teradata database server. regardless of prior certifications.?@ Assistant. 5ou may need to apply software patches as problems are found. 5ou will want to have a procedure to chec$ that the uninstall completes successfully. . . This may remove the need for a mass upgrade. !lease discuss. but there are many others. . it should be the first tas$ in the 4# migration plan. *ave database and application teams test the new TT' version.& Upgrade Teradata Too$s and Uti$ities 7ormally the TT' client software will support 1 version bac$ and . but the general rule is to upgrade your tools prior to the database being upgraded. version and any third+party tools. It is li$ely though that certain software + e. /& Upgrade Teradata Managed Server pp$ications Identify which managed servers need to be upgraded and to what version they need to be upgraded to.ome companies push TT' clients to wor$stations. versions forward. communicated with your users and opened your change control you can proceed with applying any required client application updates. Include tests of TT' along with any third+party tools used. The Teradata 84#" driver. at the the Teradata Tools and Utilities Installation Guide for a complete list and detailed installation instructions. The acronym . Arcmain + will still need to be upgraded. different versions will be available for the database version in question. In the past various issues have surfaced during uninstalls. If this cannot be done prior to the database upgrade.Customer Best Practices for Teradata Software Upgrades -& Upgrade C$ient Software 8nce you have identified all dependent client software in your environment. with Teradata. 4epending on the timing of when TT' is to be installed. This is something you want to do long before doing the Teradata server software upgrade. It is recommended that the managed servers be upgraded prior to the database upgrade. *owever. In that case you may wish to have each user download the latest install pac$ages from a central source. This includes software that runs on -indows as well as various flavors of '7IB and @inux. it is very common for users with wor$station administrative rights to install their own TT' software. Investigate which version of TT' should be installed. . The remainder of this section will focus on the Teradata+supplied Tools and 'tilities (TT'). Identify servers and wor$stations that need upgraded versions of the Teradata client tools. li$e leftover 4@@s and registry entries.

0a$e sure you have representation from the following types of groups: • • • • • • 7et#ac$up/7et:ault . "ommon #A6 software is A6"0AI7 on mainframes. Also verify the master catalog is in good shape and has a good bac$up. After those are upgraded and running bac$ups on the local drives successfully.Customer Best Practices for Teradata Software Upgrades These $ey steps should be used when upgrading a managed server. The #A6 master server is typically upgraded first.ystem admin .) Tape silo server support (if present) Any tape library server support Teradata 4#A/. J J J J J J J J "reate plan for upgrade Initiate change control process for both Teradata and local "ommunicate outage to users if they access managed server 6un full bac$up of managed server Turn managed server over to ". . It is a good idea to save any custom configuration files present on the master server before the upgrade (&ava. 8nce the #A6 master server software is upgraded. you are ready for the media servers to be upgraded. !art of the upgrade process is to convert the master catalog for use on the new version. comprehensive bac$up prior to the upgrade in case any files need to be restored. After the software has been upgraded on the master server. !atch @evel.hould your corporation have certain standards of software. perl. in the event additional time is required for the upgrade process. chec$ the Teradata roadmap to determine which versions of software are compatible with the version of database software you are upgrading to. .6 to apply upgrade 6un test cases once upgrade complete "ommunicate to users that managed server is available "lose change control %+& Upgrade B R Software 5our bac$up and recovery (#A6) software may need to be upgraded prior to the database upgrade. 8. or begin the process of certifying them as soon as possible. :erify there are no licensing issues with upgrading to the new software version. The master server should also have a full.ymantec) and 7et:ault (#a$#one) on the open clients.ilo . 7#'/7et:ault.). the Teradata software may Partners Service Focus Team ') . and 7et#ac$up (. In addition to verifying #A6 software compatibility. Tape . irst. etc. you=ll need to ta$e inventory of all system software levels in use in the environment (TT'. environment will continue to support this upgraded software. nbu. you will save significant time later. several groups may need to be involved in this process. run several tests to validate any older versions of media server clients still wor$ with the new master server.hould an upgrade to the #A6 platform be necessary. 4epending on your corporate structure. ma$e sure the new versions are permitted for use within your company.ymantec or #a$#one) #A6 0aster and 0edia server support (8.upport (..oftware. you=ll need to verify the 8. #y understanding your options up front.) as the upgrade process will probably write over them.omeone that has or can verify appropriate permissions for the upgrade process on all platforms 5ou should schedule your #A6 upgrade around any critical bac$ups your location may require. etc.

control settings. "lean+up unnecessary data and ob&ects 6un scandis$ and chec$table on the existing system. settings. All+amp bac$ups are preferred over clustered bac$ups if the amp configuration will be different after the upgrade. #e aware of new TT' patches that are released in the meantime that may resolve newly discovered performance or connectivity issues. . :erify you can log on using A6" to your target Teradata database. !I80.ys. Loin Indexes. This is a typical list of things to do: • • • • • 8pen change "ontrols K Teradata E local.. If you use &ournaling. I"'. 6un full bac$ups of important data. document your new software levels and ma$e sure you test again once your Teradata database is upgraded. 4isable 4#?@ and offload to history repository. It is a good idea to reboot nodes one wee$ prior to upgrade. in case you need to do a full recovery if something goes wrong. (in that order). <. %nsure you have bac$ups of 4#. 'ninstall A6". T4-0. 4o this enough in advance to allow time to address any problems discovered. B"T@. I"'. consider performing a complete 4#" system dump and restore to ensure that that the new version of Arcmain will restore the AoldA version of the system in case of disaster recovery If all runs well. That may require an unreasonably long restore window. you may need to drop your &ournal tables prior to the upgrade. 6emember that cluster bac$up datasets must be restored serially to a different amp configuration. Triggers and '4 s. Install the new version of T4% or TA6A. 6ecord the current software levels of all Teradata software in the event you need to bac$ off the upgrade. A6" (in that order). "lean reserved words (including T!T). !.pool. etc. 84#". Install the new versions of <.. These should be dropped prior to the upgrade. 6es'sage. %%& Teradata Pre0Upgrade Preparations This section concerns those tas$s that need to be done shortly before the Teradata software is upgraded. *ere is a typical #A6 upgrade scenario example using 7et#ac$up: • • • • • • • • • • • • • 'ninstall T4%/TA6A..Customer Best Practices for Teradata Software Upgrades be upgraded. !erform your all+system validation again: #ac$up all local media server drives (non+Teradata bac$up) This validates 7#' can communicate with the master server and tape drives #ac$up a test Teradata table using all media servers This validates 7#' can communicate with Teradata 6estore a test Teradata table Test a scheduled bac$up within 7#' to validate the scheduling still wor$s as expected If you have a separate test or development Teradata server. "@I. <enerate 44@s of *ash. "@I. 84#". "lean leftover . !I80.ec4efaults. • • • • • • Partners Service Focus Team '* .

-hile the software upgrade itself will typically be done by your Teradata ". you need to find the max value of the id generated.hutdown open systems bac$up application (7et#ac$up. these are last+minute functions the customer 4#A may need to perform: • • • • • • • • • • • ?uiesce the system Abort remaining user sessions #ac$up 4#" #ring down any T4!s 4isable the system being upgraded in the :iewpoint configuration and/or shutdown Teradata 0anager server . (as an example.6 to perform the software upgrade %(& Post0Upgrade Steps After the ". remember to grant the appropriate dump/restore privileges on them and add them to your #A6 scripts. The 4#A would then perform a sequence of functions.tarting with T4 12. cron. Triggers and '4 s have been dropped Turn the system over to the Teradata ". or any daily archiving of dictionary tables ensure that any dictionary changes implemented by this upgrade are understood.TA6T.6.idcol after you have restored.6 during the outage window. !4"6) If you have tables with Identity "olumns. the actual upgrade may begin. %nsure that you have discussed these with the ". This should only ta$e a few minutes.Customer Best Practices for Teradata Software Upgrades • • • • • • !urge ampusage over 1MF days old. -IT* value to the max captured value plus one.6 during the outage window. he or she will turn the system bac$ over to the 4#A.6 has completed and validated the upgrade. capture the max value of the column immediately before the upgrade. If you use identity columns in one table to generate the $ey of another. Partners Service Focus Team '+ . you will need to carry out a table change and set the . If these values are lower than the value you captured. etc.ys. Loin Indexes. run scandis$ and chec$table to verify the rest of the file system is clean. If you have to restore such tables.A Turn off access logging before the upgrade . including: • • • If not performed by the ". #ac$up 4#" and any other critical databases. chec$ the Avail:alue in dbc. If any new system databases were created as part of the upgrade. 7et:ault) 4isable unnecessary user I4=s . %'& Teradata Upgrade 7ow that the system is fully prepared. If not performed by the ".top any &ob schedulers such as Auto. there are several activities that the customer 4#A must perform before and after the upgrade.1F and higher. run chec$table 4#" only at level 2. 6un chec$table !ending 8! and resolve any identified issues %nsure that all *ash. 6esolve chec$table issues (tables in a pending load status).6 performing the upgrade so you understand and execute them appropriately.

5ou deserve itN Partners Service Focus Team '.ecurity. . programs. This often gets changed. This information will be invaluable for planning the next ma&or upgrade. :isual %dge.tart/confirm T4!As and enable logons. If you are maintaining an upgrade plan template document (see the !ro&ect 0anagement section above). "lose "hange "ontrols K Teradata E @ocal. !ublish results. . etc. B"T@ and !. 8@%@oad. 4#.hortly after the upgrade is complete and users are happily using the system you will want to have a pro&ect wrap+up meeting. !riority scheduler. .ystem .0. #T%?-in. etc. procedures.ys. The upgrade scripts would have identified and recompiled any Teradata . Teradata 0anager. 6estart open systems bac$up application. connectivity.lessons learned/ session and document what went well and what could be done better next time. 6un test program to validate all settings. 7otify customers of system availability.ysH"alendar. 0ay need to ad&ust user spool settings if number of amps changed. If you have to restore a !!I table you may need to revalidate the !rimary Index afterwards : AAlter table x revalidate primary indexA. this would be a very good time to update it with any new learnings. etc.tored !rocedures (T4. 6ecreate &ournal tables (if any). This command normally runs quic$ly. cron. 6estart 4#?@. Teradata Administrator. settings. "hec$/reset T4-0. Loin Indexes.control.e. bac$up.Customer Best Practices for Teradata Software Upgrades • • • • • • • • • • • • • • • • • • • • • 6un collect stats on application tables if recommended for this upgrade version. 4#" tables. 0a$e sure the default date format is set correctly.?@ Assistant. #T%?. The upgrade will not have recompiled any stored procedures whose code is stored outside the system 6estore 44@ for system databases that you may have modified (i. 6estart &ob schedulers such as Auto. Test applications such as .ign off on user acceptance of upgrade with Teradata. as before.!). Triggers and '4 s that were dropped prior to the upgrade. 4#A regression testing. Access logging. 6ecollect if necessary. A?0. %)& Project C$oseout . 6ecompile and test any user stored procedures. TA. At this point you could run your post+upgrade benchmar$s and compare them to your pre+upgrade benchmar$s. :alidate statistics are collected as should be on 4#" and user tables. The pro&ect manager should lead a . ."A@%74A6). 6estart :iewpoint monitoring by enabling the system on the :iewpoint servers and/or restart the Teradata 0anager server 6ecreate *ash. *it your management up for a party. . restore etc.

0embers represent the concerns of Teradata customers by serving as catalysts for service improvements. . !lease let us $now of any comments or suggestions you may have. T at our website: http://www.teradata+partners. The members of the . .ee you at !artnersN 5ou can find our contact information and more about the .ervice ocusTeam Partners Service Focus Team '- .Customer Best Practices for Teradata Software Upgrades %*& C$osing The . T sincerely hope that you found this document useful.teering "ommittee. providing ongoing feedbac$ to Teradata and the !A6T7%6. 'ser <roup that wor$s closely with Teradata on issues related to support services and other areas that fall beyond the scope of product enhancements. T is a committee of the !

Sign up to vote on this title
UsefulNot useful