Upgrading Oracle E-Business Suite 11.5.10 to CU2

Some notes I collected from the exercise of upgrading Oracle E-Business Suite 11.5.10 to 11.5.10 CU2^*, on Sun Solaris:

1. [Middle-tier] Apply patch 4318672 on all application server nodes
   
   
   • Enable maintenance mode by running adadmin.
     
     
   • Apply patch 4318672 with the help of adpatch tool.
     
     
   • Carefully read README.txt of 4318672, and run Technology Stack Validation tool in both middle- and db-tiers.
     
     Note:
     
     
     • Set PARALLEL_MAX_SERVERS parameter to the default value returned by show parameter cpu_count. For example, if the database is running on a SunFire T2000 server, set PARALLEL_MAX_SERVERS to 32.
       
       
     • [DB-tier] When prompted for applications context file, supply the output of echo $CONTEXT_FILE environment variable.
       
       
     • After running Technology Stack Validation tool, the generated html reports from middle- and db-tiers should have an 'ALLPASS' status. Otherwise, fix the errors and re-run the TSV tool until it achieves ALLPASS status.
   
   
2. [Middle-tier] Apply patch 4229931 on all application server nodes
   
   
   • Apply patch 4229931 with the help of adpatch tool.
     
     Location of adpatch log file: $APPL_TOP/admin/<DBInstanceName>/log/adrelink.log.
   
   
3. [Concurrent Processing node] Apply patch 4297568
   
   
   • Enable maintenance mode by running adadmin tool, if concurrent managers are not running on the same machine where all application server processes are running; then apply patch 4297568 by following the special instructions posted in README.txt file.
     
     Note:
     
     • Do NOT use adpatch tool to apply this patch, 4297568. Read the instructions of README.txt.
       
       
     • Without this patch, 4297568, CU2 maintenance patch, 3480000, may fail with error messages like:

       ld: fatal: file  /ebiz/visappl/sht/11.5.0/lib/ilog/5.1/libcplex8.a: 
       open failed: No such file or directory
       ld: fatal: File processing errors. No output written to /ebiz/visappl/demoappl/mst/11.5.0/bin/MSTCPP

       See Metalink document 311635.1 for more.
       
       
     • Some executables need to be re-linked as part of this step. Re-linking can be done in two ways:
       
       
       1. Using adadmin tool.
          
          Navigation: Maintain Applications Files -> Relink Applications Programs. This step re-links all the executables of the application.
          
          
       2. To re-link one or more applications' executable programs, run adrelink from the operating system shell:
          
          Syntax:
          adrelink force=y "<product> <module>"
          
          eg., To re-link MSO: MSONEW, run:
          
          adrelink force=y "MSO MSONEW"
          
          Shutdown all concurrent managers before running adrelink.
     
     
     
   • Disable maintenance mode by running adadmin, if concurrent managers are not running on the same machine where all application server processes are running.
   
   
4. [Middle-tier] Apply release 11.5.10.2 maintenance pack, 3480000
   
   
   • Apply patchset, 4712852, with the help of adpatch tool.
     
     
   • Apply release 11.5.10.2 maintenance pack, 3480000, with the help of adpatch tool. Spare some time to read Metalink document 316365.1, before applying the maintenance pack.
     
     Note:
     
     
     • Stop all application server services including concurrent managers before running adpatch on 3480000 (CU2 maintenance pack). Failure to do so may result in the following error(s):

       ATTENTION: All workers either have failed or are waiting:
               FAILED: file afcmgr.odf on worker 1
       ATTENTION: please fix the above failed worker(s) so the manager can continue

       When such an error occurs, do the following:
       
       
       • Open up another shell and shutdown all services by running adstpall stop apps/apps command.
         
         
       • Run: adctrl
         
         • Check: 1) Show Worker Status.
           
         • 2) Tell worker to restart a failed job
         
         After this step adpatch resumes automatically.
         
         
       • adworker log file(s) default location: $APPL_TOP/admin/<DBInstanceName>/log.
     
     
   • Troubleshooting:
     
     
     • ERROR: file azstrctall.ldt on worker 1
       
       Follow the instructions of Metalink document '331284.1 Applying 3480000 Patch --- azstrctall.ldt failed --- ORA-20001: The specified api_code does not exist'.
       
       
     • FAILED: file AsgRunInst.class on worker 1
       
       Follow the instructions of Metalink document 270156.1. In short, skip the failed thread with an hidden option {of adctrl} : 8) Skip & Restart for worker thread 1. Run the failed thread manually, later.
   
   
   
5. [Middle-tier] Disable maintenance mode by running adadmin

_________
^* CU2 = Consolidated Update 2.

Reference Document:
Metalink document 316366.1 11.5.10 Oracle E-Business Suite Consolidated Update 2 (CU2).

Technorati tags:
Oracle | Oracle Applications | E-Business Suite