IBM DB2 10 Migration Planning and Very Early ... - GSE Belux
IBM DB2 10 Migration Planning and Very Early ... - GSE Belux
IBM DB2 10 Migration Planning and Very Early ... - GSE Belux
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Keys to customer migration success<br />
1. Plan for continual application of preventative service<br />
– Need to stay more current on HIPERs at this stage in the release take up cycle<br />
– Apply preventative service every 3 months<br />
• Two “major” <strong>and</strong> two “minor” releases<br />
• Refresh of the base every 6 months (“major”)<br />
• Each base should be based on latest quarterly RSU as opposed use of PUT<br />
• In addition, two ‘minor’ packages covering HIPERs <strong>and</strong> PEs in between time<br />
– Augment by exploiting Enhanced HOLDDATA on a weekly basis before<br />
production cutover <strong>and</strong> continue thereafter<br />
• Identify <strong>and</strong> pull all applicable HIPERs <strong>and</strong> PE fixes<br />
• Expedite the most critical PTFs into production<br />
2. Perform application regression <strong>and</strong> stress testing is the best way to keep<br />
‘fires’ away from production<br />
3. Build a realistic project plan<br />
– Avoid crash project<br />
– Allow contingency for ‘bumps in the road’<br />
– Involve applications teams early<br />
• Investigation of incompatible changes <strong>and</strong> fix up<br />
• Testing<br />
9<br />
© 2011 <strong>IBM</strong> Corporation
Change language