Archives of the TeradataForum
Message Posted: Mon, 03 Mar 2003 @ 23:10:54 GMT
we will migrate from V2R4.1.3 to V2R5 on the weekend from 22.3.
Steps to do before:
In your production process:
1.) Get NCR in to check for "reserved words" and to calculate the "estimated update time". (For time planning)
2.) Install TTU before on a test- or backup system: Check if all your fastloads, multiloads, tpumps, fexps, bteqs ... are working (against your current release).
3.) What about your OWN (or 3rd party) maintenance and administration scripts? --> Try to get at least a R5-Demo under Windows and run your scripts against it !
4.) Check for sloppy code (there has been a thread before...)
In your reporting process:
1.) Check for "Default Date" and dates as they are used in your reporting systems (OLAP tools).
2.) Check for sloppy code (there has been a thread before...)
3.) Check if your applications are working with new ODBC and TLI Drivers.
In your operational process:
1.) Make a backup. (NCR will recommend anyway)
2.) After update, make another backup (NCR will recommend anyway)
My personal stuff:
1.) I saved all the relevant "explains" of the last 2 months (for reference).
2.) Save the current execution times for loads, exports, bteqs (for reference).
That's it so far, I'll keep you updated, but as far its looking quite straigthtforward!
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|