Note:-- If your are planning to upgrade your Oracle Database to 10g, it is important that your are already at 11.5.10.2. This is required because of few bugs associated with this senario. As a result, the upgradation of your database to Oracle Database 10g is done after the application of the MP.
1. Verify space.
Verify that you have at 10-15GB free space under your APPL_TOP, ORACLE_HOME and DATA_TOP.
2. Pre-upgrade health checks.
Perform health-checks and make a note of what is working and what is not, before you proceed with the upgade. This is important, since if you encountered some issues after the upgrade you can make sure whether upgrade has brought those issues or not. If you encountered any issues during the health checks, do try to trouble shoot those as much as possible.
3. Verify the free space in the SYSTEM tablespace.
select sum(bytes)/1024/1024/1024 "free_space" from dba_free_space where tablespace_name ='SYSTEM';
The free space in the SYSTEM tablespace must be atleast 1GB.
4. Take a list of invalid objects before the upgrade.
create table apps.invalids_before_upgrade as (select object_name, object_type, owner from dba_objects where status='INVALID');
5. Bring down the instance and take a cold backup.
6. Place the database in NOARCHIVELOG mode and bring the listener up.
While bringing the database up, put it in NOARCHIVELOG mode to avoid the generation of unnecessary archive logs.
sqlplus "/ as sysdba"
startup mount
alter database noarchivelog;
archive log list
alter database open;
exit
At this point I would say, you can be sure that you have taken care of most the activities which has to be done before the upgrade. As best practices there are few database init.ora parameters which can be modified. I talk about it later.
7. Identifying customizations (If your instance is already autoconfig enabled).
Take a backup of the context file (xml file).
Run adchkcfg.sh.
eg. $AD_TOP/bin/adchkcfg.sh contextfile=$APPL_TOP/admin/<
The above command will execute the adconfig command in test mode and generate the report containing the differences.
cd $APPL_TOP/admin/_/out/
ls x_*
8. Run TUMS.
The Upgrade Manual Script for the Maintenance Pack (TUMS-MP) examines your present environment configuration and create a report. The report lists out, all the required steps and the steps which can be ignored. This report is very specific to your instance and is unique.
The Upgrade Manual Script is available via patch 4238286, do follow the readme while applying the patch.
Run TUMS:--
cd $AD_TOP/patch/115/sql
sqlplus APPS/#APPS_PWD# @adtums.sql $APPLCSF/logcp $APPLCSF/log/tumsmp.html $OA_HTML
The following link takes you through a sample TUMS report.
9. Apply AD Minipack.
The latest AD patchset level is AD.I.4. It is always recommended to be at the latest AD patchset level. You will have to be Autoconfig enabled to apply AD.I. Please refer metalink Note 165195.1 for all the information about autoconfig.
If you are not at AD.I.2 (4337683), then you can apply AD.I.4 (4712852) directly.
If you are already at AD.I.2, then apply patch 4605654. It will bring you to AD.I.4.
10. Apply Patch 4104924 TXK (FND) AUTOCONFIG TEMPLATE ROLLUP PATCH K (July 2005).
Apply patch 4104924, with options=noautoconfig.
Defer the autoconfig run now. You can run it once when the upgrade is completed.
Do, run adchkcfg.sh and make a note of all the customizations the new autoconfig template files will bring in.
11. Run Technology Stack Validation Utility.
This is one of the most important pre-upgrade task along with the application of AD.I patchset. Technology Stack Validation Utility generate a report via which we can verify whether our individual Technology Stack is at the required versions. If they are not, it will also suggest you what the required level. You might then be required to upgrade those components before you proceed further. It is mandatory that the Technology Stack Validation Utility report shows an "ALLPASS".
Technology Stack Validation Utility is available via patch 4318672.
To run the Utility on each Application Tier Nodes:
On UNIX or Linux:
$ADPERLPRG $FND_TOP/patch/115/bin/TXKScript.pl
-script=$FND_TOP/patch/115/bin/txkVal11510MP.pl
-txktop=$APPLTMP -appspass=
-outfile=$APPLTMP/txkVal11510MP.html
To run the Utility on Database Server Nodes:
UNIX or Linux:
$ADPERLPRG $ORACLE_HOME/appsutil/bin/TXKScript.pl
-script=$ORACLE_HOME/appsutil/bin/txkVal11510MP.pl
-txktop=$ORACLE_HOME/appsutil
-appspass=
-outfile=$ORACLE_HOME/appsutil/temp/txkVal11510MP_DB.html
The above command are taken from the readme of patch 4318672.
Do go through the readme for the complete instructions for applying the patch and for each and every step as to how you should run the Technology Validation Utility.
You can proactively bring the technology stack components to your required levels before you run Technology Validation Utility. Database, JDK, IAS, jInitiator, Developer 6i, Discoverer,etc. are few of the components which are in general proactively upgraded.
12. Convert database to new tablespace model.
This is an optional step. Oracle Applications uses a new tablespace model based on database object type rather than product affiliation. Earlier Oracle Applications normally has to tablespace for each product, eg. GLD (for data) and GLX (for indexes). with this new tablespace mode you will have only 12 tablespaces; including your system, undo and temp tablespaces. The result is simpler to manage and requires far fewer tablespaces and operating system files.
We would be coming up with a separate Oracle Applications Tablespace Migration utility (Note 269291.1). article soon.
13. Configure database for new products and new tablespace requirements.
Apply patch 3180164. It provides scripts and instructions for adding and updating the necessary products and tablespaces. Go through the readme of this patch carefully, failure to do so can result in many failures during the application of MP.
14. Prepare AuditTrail shadow tables for update.
If you are using the AuditTrail feature, then you need to rename the associated shadow table before any new columns can be added. (All HRMS and Payroll customers using AuditTrial are affected.) Apply patch 3872242 to determine which shadow tables must be modified. Do go through the readme.
15. Install Planner libraries.
This is a conditional step. If any of the products that rely on ILOG Planner libraries have an installation status of "Installed" or "Shared," apply patch 4297568 on the concurrent processing server node, even if you don't use those products. The patch contains version 5.1.9 of the libraries. Products which require ILOG Planner libraries are END, MSO, MSR. MST, WIP and WPS.
16. Product specific steps.
The following task needs to be performed only if you are using the corresponding product.
Prepare Payables for update
Prepare Service for update
Migrate Oracle Service Contract rules and time values
Prepare Shipping for update
Prepare Oracle Depot Repair for update
Review Interaction Center certifications
Synchronize data for Mobile Field Service
Prepare Process Manufacturing for update
Prepare Marketing and Sales for update
Migrate Leads Management Data
Prepare TCA for Human Resources update
Update Oracle Applications Desktop Integrator client
Go through metalink Note 316365.1, Section 1: Pre-Update Tasks .
If you have any queries, get back to us.
17. Change password policy control (conditional).
If the profile option SIGNON_PASSWORD_HARD_TO_GUESS exists with a value of Y, set it to N. You can restore this value to Y after the application of the MP.
This concludes the pre-update tasks, we would now proceed to apply the Maintenance Pack.
No comments:
Post a Comment