Into the 11i woods with Wickes Lumber

1
Into the 11i woods with Wickes Lumber

• August 27, 2001
• Pat Reed
  Sandra Vucinic
• Wickes Lumber Risetime
  Technologies
• preed_at_wickes.com
  sandra.vucinic_at_risetime.com

2
Introduction

• Pat Reed Project Leader for all Oracle systems
  at Wickes Lumber
• Project Manager for the original Oracle General
  Ledger implementation in 1995.
• Project Manager for 11i Upgrade project.
• Sandra Vucinic Director of Oracle Solutions
  Practice at Risetime Technologies
• Over 7 years of experience with Oracle database,
  applications, development and administration
  tools.
• Assisting customers with Upgrades to version 11i
  since June 2000.
• Project roles Architect, DBA, Project Lead

3
Agenda

• Background
• Approach and Timeline
• Project Management
• 11i Project Log
• Lessons Learned
• Issues and Resolutions
• Conclusion

4
Background

• Oracle history at Wickes
• Oracle General Ledger implemented in 1995.
• Upgraded from version 10.5 to 10.7 for Y2K in
  1998.
• Oracle Assets and Oracle Receivables implemented
  in 1999.
• Migrated database to version 8i (8.1.6.2) in
  2000.
• Pre 11i version - 10.7 NCA on IBM AIX platform
• Production database 45 GB after migration to 8i
• Production and test middle tier on the same box
• GL and FA some customizations
• AR large customizations to interface with legacy
• Over 400 custom objects (sql scripts, db objects,
  reports,form)

5
Approach and Timeline

• Approach
• Scope limited to the upgrade only
• New features and functionality will be
  implemented after the upgrade
• Database upgrade to version 8i completed months
  before the 11i upgrade
• All users on NCA
• Timeline
• Analysis and planning completed in April 2001.
• First test upgrade to 11.5.3 completed in May
  2001.
• Second test upgrade to 11.5.4 completed in July
  2001.
• Planed go live date - September 2001.

6
Project Management

• Develop detailed project plan.
• Identify core upgrade team members and their
  responsibilities on the project.
• Establish weekly status update meetings.
• Categorize and track issues. Create issues log.
• Plan for extended down time during the actual
  application upgrade.
• Develop TAR and Patch logs.
• Use Oracle Upgrade Assistant Spreadsheet to track
  tasks, time and resources.
• Develop upgrade check list.

7
11i Project Log

• Assessment and Planning phase April 2001.
• Architecture and Hardware Impact
• OS (required patches and kernel parameter changes
  on db and apps servers)
• Confirmed product combination certification
• Sized apps servers on IBM AIX platform (separated
  production and test middle tier)
• Sized database servers for 11i Added space and
  memory
• Configured end users PC (new PCs for developers
  and power users 800 MHz, 128 MG memory)
• Customizations and Interfaces Analysis
• Used Vision demo database for initial analysis
• Third Party Tools (Vista Plus - Quest)
• Checked availability and certification

8
11i Project Log

• First test upgrade to version 11.5.3 May/June
  2001.
• Cloned development instance. Used AD clone
  utility provided by Oracle to perform clone.
• Re-developed customizations for AR, FA and GL.
• Tested vanilla Oracle functions and processes.
• Started end user training.
• Evaluated test upgrade. Implemented changes to
  our production database prior to the next test
  upgrade
• Modified lock box interface. We are finally
  supported...
• Assigned standard data group to custom
  responsibilities
• Developed custom views for AR tables

9
11i Project Log

• Second test upgrade to version 11.5.4 - July
  2001.
• Unit tested customizations. Developed upgrade
  check list.
• Evaluated pros and cons for going to 11.5.4
• Pros
• Technology stack patched including
• Developer 6i patch set 3. Forms screens doesnt
  lock any more.
• Jinitiator 1.1.8.7 certified for Windows NT, 98
  and 2000 clients. We can support our Windows 2000
  users.
• Database version 8.1.7.1. Terminal release for 8i
  and the longest supported by Oracle.
• Cons
• The latest product patches not included in
  11.5.4. Need to patch modules after the upgrade.
• Changes from 11.5.3

10
11i Project Log

• Second upgrade to version 11.5.4 - July 2001
• Effort paid off
• Straight forward database upgrade to version
  8.1.7.1
• Reduced number of problems during the upgrade by
  60 from the version 11.5.3.
• Reduced number of patches needed to apply prior
  and after the upgrade. Opened only a few TARs
  during the upgrade.
• Successfully configured database using rapid
  install.
• On line help installed without any additional
  patches.

11
11i Project Log

• How long did upgrade take?
• Category 1 Pre-Upgrade steps 11 hours
• Category 2 After software received - 12 hours
• Category 3 Performing the Upgrade 17 hours
• Category 4 Before using application 40 hours
• Category 5 Before using the products 1 hour
• Category 6 Before using product specific
  functions 1 hour
• Final steps Apply additional product patches
  12 hours
• Critical downtime Category 3, 4, 5, 6 and final
  steps
• 71 hours

12
Lessons Learned

• Migrate database to version 8i (8.1.7.x) ahead of
  time.
• Monitor and document your upgrade times and
  errors.
• Test vanilla Oracle functionality. Test impact
  of patches on your custom code.
• Evaluate impact of CBO on your custom code.
  Gather statistics using standard Oracle
  concurrent programs after applying patches.
• Perform dress rehearsal upgrade a week before
  your production upgrade. There should be no
  surprises.

13
Lessons Learned

• Stress test your new hardware.
• Use vision demo database for customizations
  analysis, new functionality evaluation and early
  user training.
• If new function can eliminate a customization use
  it.
• Dont underestimate DBA and technical developers
  time required to complete the upgrade.
• Make changes in you current system that will
  benefit you during the production upgrade.
• Plan for multiple test upgrades.

14
Issues Resolutions

• Problem during the auto upgrade while using
  uniform extent allocation for locally-managed
  tablespaces.
• Performance issues with applying patches
• Gathered statistic for specific tables prior to
  applying patches
• AR vs. HZ tables 11i changes
• Some Folders didnt convert.
• AR patch set D effected our custom code.
• Issue with adclone utility in version 11.5.4
• AR customer screen (ARXCUDCI) doesnt display
• Landscape reports printed one logical page on two
  physical pages
• Modified printer srw driver for Landscape style.
  
  

15
Conclusion

• Migrate database to version 8i ahead of time
• Document all your customizations
• Test impact of patches on your custom code
• Take approach nothing works for testing
• Categorize and document all issues
• Plan and conduct multiple test upgrades
• Be prepared for extended down time during the
  upgrade
• Dont underestimate the amount of work necessary
  to perform successful upgrade

16
Questions

• Pat Reed
  Sandra Vucinic
• preed_at_wickes.com
  sandra.vucinic_at_risetime.com
• [phone]
  [phone]