Oracle constantly strive and release higher versions of Oracle Applications E-Business Suite, which include a lot of enhancements, features, bug fixes, etc. It is highly recommend that you come at the latest release of Oracle Applications to enjoy all the latest features, bug fixes and to remain at the required supported level as per Certification Matrix in Metalink.
The latest release of Oracle Applications which is available to customers is 11.5.10. Infact to be precise the latest release is 11.5.10.2 (which is nothing but, 11.5.10 + Consolidated Update Patch 2). R12 the next major release of Oracle Applications is around the corner.
Performing upgrade is a major task, both from an effort as well as business point of view.
I will stuck my neck out an say, a major chunk of the budget is showered on it.
Upgrade require a lot of planning, tracking of time, continuous effort for about 2 days (for a minor upgrade, depending upon your resource capacity) and a through testing. Needless to say performing an upgrade on the test instance is mandatory. When the upgrade is performed on the test instance each of the parameters mentioned above should be monitored and recorded closely; as to how much time had been spend for planning, time taken for the execution of the upgrade, what were the issues encountered, whether the testing done after the upgrade was successful, etc. Infact you should do 'n' number of iterations on the test instance, till you are confident of achieving a successful upgrade, before even touching the production instance.
Upgrades are generally classified as Major and Minor upgrades. Major upgrades are the one where we upgrade from 10.7/11.0.3 to 11i. Note 11i to R12, will also be a major upgrade. Major upgrades bring in a whole new Technology Stack in place and usually take a lot of time compared to minor upgrades. Most of the Oracle Applications customer now are at 11i. Minor upgrades or point release upgrades are the ones were we upgrade our instance from lower version of 11i to a higher version of 11i (eg. 11.5.8 to 11.5.10.2), by applying the corresponding Maintenance Patch. Few of the Technology Stack components may get upgraded as pre- requisites/post upgrade steps.
In the following section I will be going through each and every steps involved during a minor upgrade (to 11.5.10.2).
Typically, a 11i upgrade is divided into the following sections:--
1. Pre-Update Tasks.
2. Applying the Maintenance Pack.
3. Post-Update Tasks.
4. Product-Specific Tasks.
5. Final tasks and release of the instance.
We will be going through each and every section, what all the steps involved, what all are the best practices, etc.
Section 1: Pre-update Tasks.
-----------------------------
In this section, we prepare the system for the application of the Maintenance patch. We can also proactively upgrade/configure few of the components before the applications of the MP. The versions of the Technology Stack components are validated during the Technology Stack validation utility run. The very first step in this section would be take a complete cold backup of your Oracle Applications instance, followed by putting the database in archivelog mode. It is a general practice to upgrade your database first up and proceed with the other steps.
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/
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.
Section 2: Applying the Maintenance Pack.
---------------------------------------------
1. Download the US version of the Maintenance Pack 3480000 and unzip it. Your unzip utility should be of version 5.41 (or later).
2. If you using other languages along with your US langauage, download the corresponding NLS version of the patch 3480000. If you are using 2 or more NLS languages, you can merge all the NLS version of the Maintenance Pack and applied it at one go.
References:
Oracle Applications NLS Release Notes (Note 316804.1).
Oracle Applications Maintenance Procedures (Note 289791.1).
The above 2 steps should be done, before the downtime starts.
3. Shut down application tier server processes or services.
Bring down all the Oracle Applications services down, only your database and database listener should be up.
4. Maintenance mode.
Place the instance in maintenance mode using adadmin and selecting option 5.
5. Deinstall application tier services (Windows only).
MP changes the way few services are defined and started on windows. We have to manually deinstall the services, once the Oracle Applications services are down.
Apache Server:
%COMMON_TOP%\admin\install\
Forms Server:
%COMMON_TOP%\admin\install\
TCF Socket Server:
%COMMON_TOP%\admin\install\
Fulfillment Server:
%COMMON_TOP%\util\OamkSvc.exe -sr "Oracle Fulfillment Server
iProcurement Server:
%COMMON_TOP%\admin\install\
ICSM:
%IEO_TOP%\admin\scripts\
6. Upgrade the database.
This is a conditional step. The minimum version of database required to go to 11.5.10.2 is Oracle9i Release 2. If you want to go to datbase 10g, then you must be atleast at 11.5.9.2 or 11.5.10.2. There is a bug assciated with this issue. We cannot upgrade your database to 10g, which you are at 11.5.9 or prior or if you are at 11.5.10.
Review the documnets Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0) (Note 216550.1) or Oracle Applications Release 11i with Oracle10g Release 1 (10.1.0) (Note 282038.1).
As mentioned in the pre-update section, database upgrade is invariably done as one of the first step, well before this point.
7. Apply the maintenance pack.
Apply patch 3480000. You need to applying first of the admin node, then apply it on other Oracle applications nodes. If Shared APPL_TOP is implemented, then you need to apply it only once from the admin node, immaterial of how many nodes you have.
If you are applying from 11.5.4 or earlier, you need to run Maintain multi-lingual tables from the admin node, using adadmin.
Once the MP is completed review the log file for any errors and confirm that 3480000 went through successfully.
Once US version of the MP is applied successfully, you can apply the NLS/merged NLS version of MP. You have to apply on admin node first.
Review note Oracle Applications Maintenance Procedures (289791.1).
Prior to Release 11.5.9, you were required to run AD Administration to:
Recreate grants and synonyms for APPS schema(s)
Compile APPS schema(s)
Compile flexfield data in AOL tables
Maintain Multiple Reporting Currencies schema(s)
Generate message files
Compile Java Server Pages
The above is not required now. Autopatch will do it automatically.
With we conclude this section. You are at 11.5.10.2 now.
You can confirm the same by running the following query--
select RELEASE_NAME from FND_PRODUCT_GROUPS;
Section 3: Post-Update Tasks.
-------------------------------
This comprises of few steps which has to be performed to meet the best practices and to complete the successful application of MP.
1. Apply interoperability patches for 10g.
For database 10g Release 1, apply patch 4332078.
For database 10g Release 2, apply patch 4653225.
2. Review Security Practices.
Review and follow document Best Practices for Securing Oracle E-Business Suite - v2.1 (Note 189367.1). In particular, you must explicitly grant access to any machine that requires direct access to the RDBMS, and is not a registered node in AutoConfig.
3. Register new products.
The product added in section 1 doesn't get licensed automatically. If you want to use them, you have to do it using License Manager. Review Oracle Applications Maintenance Procedures (Note 289791.1).
Section 4: Product-specific Tasks.
----------------------------------
Once you have applied the Maintenance Pack and completed all the Post-update tasks you have take care of the Product specific steps. You have to take care of only those product which you are using (Licensed).
1. Workflow .
If you are using workflow Notification Mailer and not yet updated to Java based version, you must do that now.
Review Configuring the Oracle Workflow 2.6/11i.OWF.H Java-based Notification Mailer with Oracle Applications 11i (Note 268085.1).
2. Discoverer End User Layer .
11.5.10.2 supports the use of Discoverer 10g and 4i End User Layers (EULs).
If you are using any of the following products, you must perform the Discoverer EUL implementation steps.
The products are--
ABM, AMS, AMW, BEN, BIS, BIX, CE, CN, ENI, FII, HRI, IBE, ISC, MRP, MSC, OKC, OKI, OPI, OZF, PAY, PER, PJM, PJR, PMI, POA and PSB.
Review documents--
Using Discoverer 10g with Oracle Applications 11i (257798.1).
Discoverer 4i End User Layer (EUL) Maintenance for Oracle Applications 11i (182106.1).
3. The following task needs to be performed only if you are using the corresponding product.
e-Commerce Gateway
Payables and Receivables
iProcurement
Advanced Planning and Scheduling
Human Resources
Payroll
Time and Labor
Labor Distribution
Oracle Training Administration/Learning Management
Activity Based Management
Embedded Data Warehouse
Product Lifecycle Management
Order Capture/Quoting
Sales
Marketing
Service/Install Base
Enterprise Install Base
Mobile Field Service
Go through metalink Note 316365.1, Section 4: Product-specific Tasks.
If you have any queries, get back to us.
Section 5: Final tasks and release of the instance.
-------------------------------------------------
1. Verify invalid objects.
Compare the present list of invalid objects with the one before the upgrade.
select owner, object_type, object_name from dba_objects A where status='INVALID' and not exists (select null from apps.invalids_before_upgrade B where a.object_name = b.object_name);
2. Run autoconfig.
Do run first adchkcfg.sh (check section 1, step 7) and take care of the customizations first before running autoconfig. Review Note 165195.1.
3. Change password policy control.
If you had change the profile option SIGNON_PASSWORD_HARD_TO_GUESS in the pre update tasks to 'N', then set it to 'Y' again.
4. Place the database in archive log mode.
sqlplus "/ as sysdba"
Shutdown immediate;
startup mount
alter database archivelog;
archive log list
alter database open;
5. Disable Maintenance mode, using adadmin.
6. Bring all the Oracle Applications services and perform health-checks.
Troubleshoot any issues, which you would encounter. If you encounter an issue which existing even before the upgrade, then upgrade shouldn't have brought that issue.
7. Backup.
Once you have satisfied with the health-checks, then you can bring the instance down and take a backup. Normally it is a practice to take a backup after the upgrade, to have a state of the instance (just after the upgrade) in hand.
8. Release the instance.
Bring up the services and release the instance.
All the other steps given below can be performed after the instance is released.
9. Drop MRC Schema .
The schema for Multiple Reporting Currencies (MRC) is no longer used. AutoPatch and the AD Administration utility recognize this fact and no longer maintain it. You can safely drop the MRC schema at your convenience, even after users have returned to the system.
Remove it by entering the following commands:
cd $APPL_TOP/admin
sqlplus SYSTEM/
Depending on your configuration, this script may run for two or three hours.
10. Run the "Gather schema statistics" concurrent request.
11. Apply latest consolidated online help patch .
Apply the US version of the Patch 3275245, followed by the NLS (which you are using) version of the patch. NLS version of Patch 3275245. is only required, if you require online help in that language.
12. Run the "Rebuild Help Search Index" concurrent request.
You have now completed all the steps related to upgrade. You should now monitor and attack any issues, which the users are reporting. If this is a test upgrade, you should note down all the issues encountered and try to tackle them proactively during the next iteration of the upgarde or while doing it on PROD instance. Once you get a confirm from the testing team that everything is good, you can remove all the patches downloaded and log files.
No comments:
Post a Comment