Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Mon, 25 Feb 2002 @ 18:02:44 GMT

  <Prev Next>   <<First <Prev Next> Last>>  

Subj:   Re: V2R4.1 Upgrade
From:   Yonina Schuchman

  We are currently planning the addition of extra nodes which requires a s/w upgrade on the existing nodes. We can either do a 'small' step up to a point release or a 'bigger' step up to V2R4.1.1.  


We recently completed a similar set of upgrades. We were on 4 nodes at V2R3. We added on two new nodes and upgraded to V2R4.1.1. We almost two months to complete the entire process.

Step 1 - Set up the two new nodes as a standalone system and test our applications. We upgraded MVS TUF software in a test LPAR to test our batch programs. A few developers upgraded their client software as well to participate in the testing.

Step 2 - Upgrade MVS TUF software to 6.1

Step 3 - Upgrade our 4 nodes to V2R4.1.1

Step 4 - Merge the nodes together

We allowed two weeks between step 3 and 4 to shake out any production problems. This was the most successful upgrade we have ever had. I lost one small table in the entire process because it was in a MULTILOAD state, but I was able to restore it from an archive.

Those who use WINDDI and other Teradata Manager tools must upgrade their client software to use the new version. Those who only use the ODBC driver (business users) are not obligated to upgrade unless they need new functionality. The ODBC driver V3.0.0 that comes with the new software is very buggy. You must upgrade to 3.0.1. We have not upgraded our business users yet, because even 3.0.1 has problems with numeric datatypes. We are waiting for the next ODBC release.

Yonina Schuchman

  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 28 Jun 2020