pre-upgrade steps

1. storage preparation: nfs mount ready
   
2. backups
   
   • database snapshot
     
   • oci/voting disks backup
     
   • ocrconfig -showbackup
     
   • ls -l /export/home/orarac/oracle_base/oracle/product/10.2.0/crs/cdata/crs
     
   • crsctl query css votedisk
   • dd if=/oradata/ocfs1/voting1 of=/export/home/oracle/backup/voting1.bk bs=4k
   • oracel homes: crs, asm, db
     
3. Grid Infrastructure upgrade
   
   • rolling upgrade not possible for production because of asm version <11.1
     
   • swing upgrade might be necessary for production environment that requires minimum downtime
     
   • test, stage environments can use the rolling upgrade if ASM is not used
     
   1. os upgrade/patches
      
   2. out of place installation/upgrade
      
      • runcluvfy.sh
        
      • /tmp/CVU_11.2.0.3.0_orarac/runfixup.sh
        
      • sysctl -p
        
      • runcluvfy.sh
        
   3. Verify that the upgrade has completed by using the command crsctl query crs activeversion.
4. db software binary upgrade
   
5. backups
   
• db snapshot
  
• oci/voting disks backup
  
• all configuration files
  
6. database pre-upgrade steps
   
   1. run the pre-upgrade information tool @utlu112i.sql
      
   2. check the integrity of the source database with dbupgrdiag.sql
      
   3. optimizer statistics:
      
      • dbms_stats.gather_dictionary_stats (This procedure gathers statistics for dictionary schemas 'SYS', 'SYSTEM' and schemas of RDBMS components.)
        
      • backup the existing statistics for existing schemas to revert/import back the statistics once the upgrade is successful if necessary
        
   4. dictionary corruption checking
      
   5. ensure no media recovery is required
      
   6. ensure no files are in backup mode
      
   7. ensure no pending distributed transactions
      
      • ensure aud$ owned by sys and in system tablespace (n/a)
        
   8. prepare pfile and other configuration files for the new Oracle home
      

database upgrade steps

1. blackout start
   
2. stop listener and disable all batch and cron jobs
   
3. shutdown apps
   
4. turn off cluster setting, archive logging
   
5. shutdown db
   
6. cold backup(take a sanpshot)
   
7. update oratab to point to the new home and update environment variables
   
8. startup upgrade
   
9. run catupgrd.sql
   
10. shutdown db (automatically)
    
11. startup db
    
12. migrate baseline data with catuppst.sql
    
13. check the integrity of the source database with dbupgrdiag.sql again
    
14. timezone upgrade to 14 (use DBMS_DST package)
    
    • Actions For DST Updates When Upgrading To Or Applying The 11.2.0.3 Patchset[ID 1358166.1]
      
    • instruction: Updating the RDBMS DST version in 11gR2 (11.2.0.1 and up) using DBMS_DST [ID 977512.1]
      
    • it might be not necessary, if timezone is not used in apps
      
15. turn on cluster setting, archive logging, adjust compatible
    
16. create spfile
    
17. Oracle Text upgrade (may be skipped or moved to post-upgrade, need verify)
    
18. shutdown db
    
19. upgrade the Oracle Clustware configuration
    
20. startup db and services
    
21. backup: snapshot
    
22. start listener and enable all batch and cron jobs
    
23. startup apps
    
24. qa verification
    
25. blackout end
    

post-upgrade tasks

1. monitoring
   
2. miscellaneous configuation upgrade
   
   • Oracle text
     
   • OEM
     
3. cleanups
   
   • unlock/uninstall previous clusterware installation
     
   • uninstall previous asm/database installation
     
   • remove old logs/obsolete backups