1) Install the 11.5.9 Software
2) Perform the post installation steps:
a) shut down the applications
b) Download the interoperability patch 3830807
c) Relink all Oracle Applications executables using the AD Administration by choosing "Relink Applications programs" from the "Generate Applications Files" menu.
d)Restart the Oracle applications processes
STEP 1:Pre-Update Tasks
1)Apply the TUMS-MP patch:
The Upgrade Manual Script for the Maintenance Pack (TUMS-MP) examines our current configuration and creates a report detailing which of the steps in these instructions we must complete and which steps we can ignore.
Download the patch 4238286 and follow the README.txt of the 4238286 TUMS UTILITY FOR THE 11.5.10 MAINTENANCE PACK.
PREREQUISITES:
Before applying this patch you must have applied AD Mini-pack AD.G or later
So we need to apply AD-Minipack first.
Applying AD Mini-Pack AD.G or later:
Steps to Applying AD Mini-Pack:-
Download the MINIPACK 11I.AD.I.5 Patch (5161676) and follow the README.txt . and apply the patch .
This patch contains u5161676.drv driver.
Applying the TUMS-MP patch:
a)Ensure that the database parameter UTL_FILE_DIR is set to a writable directory
where the TUMS for 11.5.10 Maintenance Pack report will be created.
b)Apply the following driver file using adpatch: u4238286.drv
While applying the TUMS-MP patch we got the error :
Error:- database is missing important grants on SYS objects.
To FIX this Error:
1)Log on as the database server owner, and set the environment of database server. Create a directory called $ORACLE_HOME/appsutil/admin and copy the $APPL_TOP/admin/adgrants.sql to that directory.
2) Connect to the database as the SYS user and run adgrants.sql passing the name of the schema containing FND tables.
$ cd $ORACLE_HOME/appsutil/admin
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> @adgrants.sql APPLSYS
c) After fix the error , applying the patch again .
d) After applying Patch, Generate the TUMS report by executing the following command:
$ cd $AD_TOP/patch/115/sql
$ sqlplus
A report file called tumsmp.html will be created in the /usr/tmp directory.
2)Update AutoConfig technology stack templates:
Download the TXK AUTOCONFIG TEMPLATE ROLLUP PATCH I patch(5985992)
and follow the README.txt.
This patch must be applied to all application tier server nodes (Forms,Web, Concurrent Processing, Admin) as the Applications file system owner.
Before Applying this patch:
1. Change the directory location to
$PATCH_TOP/5985992/fnd/patch/115/bin .
2. Run the Validation script as :
txkValidateRollup.sh appspass=(apps database password)
3 . Review the report named txkValidateRollup.log , created in the
same location where the script was executed.
In VallidateRollup report we get following error:
ERROR: ORA-00904:”SUUPORT_DB”:invalid identifier
To fix this Error we need to apply:
(i) the patch 2278688(Oracle Self Service Framework Version 5.6E)
apply c,d and g drivers
(ii) the patch 2697284(OAM 2.1.1 pre-requisite rollup patch )
apply c,d and g drivers .
(iii) the patch 2949264 (Concurrent processing rollup patch )
apply c,d and g drivers.
(iv)the patch 4173121
After opening the $APPLTMP/txkValidateRollup.html file , i got some failures..
FAILURE:
Technology Components Component Version/Value Status
Oracle 9i Application Server patchset version FAIL
System is Autoconfig enabled and the Autoconfig context file and the Autoconfig context template are in sync . FAIL
SOLUTION:
Download and apply Oracle 9i Application Server patchset version (3072811) .
How to Aplly the PATCH (3072811):
- Stop Oracle HTTP Server by doing:
$ORACLE_HOME/Apache/Apache/bin/apachectl stop
– set ORACLE_HOME environment variable to iAS ORACLE HOME.
– Unzip the patch.zip, then run the following command:
./patch.sh install
– Unzip oprocmgr.zip, and run the patchconf.sh
– Start Oracle HTTP Server by doing:
$ORACLE_HOME/Apache/Apache/bin/apachectl start
System is Autoconfig enabled and the Autoconfig context file and the Autoconfig context template are in not sync :
Run the AutoConfig....
How to Apply TXK AUTOCONFIG TEMPLATE ROLLUP PATCH I Patch:
This patch contains the following driver file to be applied with
AutoPatch: u5985992 .drv
After Applying this Patch:
1. Update the RDBMS ORACLE_HOME file system with the AutoConfig files by performing the following steps:
On the Application Tier:
a)Source the environment file.
b)Create the appsutil.zip file by executing:
$ADPERLPRG $AD_TOP/bin/admkappsutil.pl
On the Database Tier:
a)Copy the appsutil.zip file to the
b)unzip -o appsutil.zip
c)Run AutoConfig by executing:
2. If your appsweb.cfg contains specialized configuration entries
within its "BEGIN CUSTOMIZATION" and "END CUSTOMIZATION" section,
then we must copy that section to appsweb_
3. Stop the application server processes using the script adstpall.sh .
4. Restart application server processes using the script adstrtal.sh .
3)Install and run the Release 11.5.10 Technology Stack Validation Utility:
This utility performs a series of tests that validate the technology stack components of a Release 11i system.
Download the Technology Stack Validation Patch(3996414) and follow the README.txt
Apply this Patch:
This patch must be applied on all application tier server nodes.this patch contains u3996414.drv driver.
After Applying this Patch on each application tier server nodes:
Step 1. Update RDBMS ORACLE_HOME with AutoConfig files:
* On the Application Tier (as the APPLMGR user):
. Log in to the APPL_TOP environment (source the environment file)
. Create appsutil.zip file
$ADPERLPRG $AD_TOP/bin/admkappsutil.pl
. This will create appsutil.zip in $APPL_TOP/admin/out .
* On the Database Tier (as the ORACLE user):
Copy the appsutil.zip file to the
. cd
unzip -o appsutil.zip
Step2.Run the Technology Validation Utility:
1. Source the Applications environment file as the owner of the
application tier file system.
2. Ensure that environment is set correctly by executing:
$ $ADPERLPRG -version
3.Run the technology validation utility using the following syntax:
$ADPERLPRG $FND_TOP/patch/115/bin/TXKScript.pl
-script=$FND_TOP/patch/115/bin/txkVal11510MP.pl
-txktop=$APPLTMP
- appspass=(apps password)
-outfile=$APPLTMP/txkVal11510MP.html
After running script one report will be generated in :
/d02/applprod/prodcomn/temp/txkVal11510MP.html this location.
After opening the $APPLTMP/ txkVal11510MP.html file , i got some failures..
FAILURE:
Technology Components Component Version/Value Status
Client library version in iAS Oracle Home FAIL
Oracle ModPLSQL version for Oracle HTTP Server FAIL
Developer 6i version FAIL
SOLUTION:
1) Apply the 8.1.7.4 patch set 2376472 (32 bit version) to the iAS Oracle Home.
After applying the patch, source the Applications environment files, then run the following script to update required iAS components:
txkrun.pl -script=InstSSLFix
2) For Oracle ModPLSQL version for Oracle HTTP Server:
Apply patch 3835781 to update modplsql version in the iAS Oracle Home to 3.0.9.8.5d
How to Apply Patch 3835781:
a) We Apply this Patch to the IAS_ORACLE_HOME. First set the ORACLE_HOME to iAS top.
b)Change the current working directory to $PATCH_DIR.
c)Identify the Oracle databases serviced by mod_plsql.
- Identify the setting for the environment variable WV_GATEWAY_CFG.
For default installs, this value is configured in the file
and has a value of
– Open the file as pointed by this environment variable.
– Search for each unique occurrence of 'connect_string' and
use the database connection information to identify which database
instances need to be patched up.
d) For all such database instances,
- Verify that we can connect to the database
- Issue the "sqlplus /nolog"
– At the SQL prompt, issue "conn sys/sys_password@conn_str as sysdba"
– Invoke the following command to patch up the OWA packages in the SYS
schema
./patch.csh -m sysobjects -o
e) Stop the Oracle HTTP Server
f) Issue the following command to patch up mod_plsql
./patch.csh -m midtier -o
g) Restart Oracle HTTP Server
3) Developer 6i Forms version:
11.5.10 Maintenance Pack requires to apply Developer 6i Patch set (Forms 6.0.8.24) or higher. We refer to Oracle MetaLink Note 125767.1 to 'Upgrading Developer 6i with Oracle Applications 11i' to upgrade.
1) Download and Apply the Developer 6i Patch 4948577
2) Download and Apply the additional Developer 6i Patches:
5713544,4261542,5216496,5753922,6195758,5938515.
3) Relink Applications Executables on UNIX Platforms.
- After applying the Oracle Developer 6i Patch on UNIX platforms, we must relink several Oracle Applications executables to include Developer patch changes. The executables are f60webmx, ar60run , ar60runb, ar60rund, and are all owned by FND.
4) Download and Apply The Oracle Application Interoperability Patch 4888294
5) Apply the Linux interoperability patch 3830807 and 4586086.
6) Verify our upgrade
- Verify that the fndforms.jar and fndewt.jar JAR files have been rebuilt by checking the timestamp for both files in the $OA_JAVA/oracle/apps/fnd/jar directory.If the timestamp is not current , then run the AD Administration Utility (adadmin), select Generate Product JAR Files . If we have applied Developer 6i Patch 6 or above, verify that the PL/SQL version installed is 8.0.6.3.x. You can run '$ORACLE_HOME/bin/f60gen help=y' to display various component versions.
Run the Utility on Database Server Nodes:
1. Source the Database Oracle Home environment file on database server node
as the owner of database server oracle home file system.
2. Ensure that environment is correctly set by executing:
$ $ADPERLPRG -version
3. Run the technology validation utility using the following syntax:
$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
After running script one report will be generated like this:
Reportfile /d02/db prod/proddb/9.2.0/appsutil/temp/txkVal11510MP_DB.html generated successfully.
Then review and correct any errors reported and re-run this script until all tests pass.I
got Following Errors:
Technology Components Component Version/Value Status
Database version from dbms_utility FAIL
Amount of temporary tablespace in MB assigned to the Apps Schema FAIL
"_B_TREE_BITMAP_PLANS" Database parameter FAIL
"O7_DICTIONARY_ACCESSIBILITY" Database parameter FAIL
SYSTEM tablespace size in MB FAIL
SOLUTION:
1) Database version from dbms_utility:
11.5.10 Maintenance Pack requires that your Oracle 9iR2 database version to be 9.2.0.4.0 or higher.So we have to Apply 9.2.0.8 PatchSet in the database Tier.
2) Amount of temporary tablespace in MB assigned to the Apps Schema:
The APPS schema must have at least 1024MB of temporary tablespace. So we need to increase the temporary tablespace to meet this requirement.
SQL> alter tablespace temp add tempfile '/d02/d02/oraofdb/ofdbdata/tempfile02.dbf' size 2000 M;
3) _B_TREE_BITMAP_PLANS" Database parameter:
We must set the "_B_TREE_BITMAP_PLANS" database parameter on the database to "FALSE".
4). O7_DICTIONARY_ACCESSIBILITY" Database parameter :
11.5.10 Maintenance Pack requires the value of "O7_DICTIONARY_ACCESSIBILITY" database parameter to be "FALSE".
5).SYSTEM tablespace size in MB:
11.5.10 Maintenance Pack requires SYSTEM tablespace to have minimum 9216 MB of space. So we increase the size of the SYSTEM tablespace by issuing the following command:
SQL> alter database datafile '/d02/db prod/proddata/system01.dbf' resize 10000 M;
Sahu completed upto here... tomorrow i will start.
4)Configure database for new products and new tablespace requirements:
Download the patch 3180164 and open the readme.html of the patch and follow the instructions.
The tablespaces of Oracle Applications production and test databases were organized according to the Optimal Flexible Architecture (OFA) standard, which meant that each product had its own two tablespaces
The ad/patch/115/sql subdirectory of this patch contains two SQL scripts that are used to create or update the tablespaces:
- adgnofa.sql (for systems using OFA)
- adgncons.sql (for systems using OATM)
Running the tablespace creation/update scripts
- We are applying this patch to a system that uses OFA, perform following
tasks on the administration server node:
a) Change directories to the ad/patch/115/sql subdirectory of this patch.
b) Run adgnofa.sql in the following manner:
$ sqlplus
c) The adruncts.sql and adcrtbsp.sql scripts will be created in the current directory. Open this adcrtbsp.sql in a text editor and looking for "create tablespace" commands. Make changes to them to give the datafiles locations as necessary.
d) Run adruncts.sql in the following manner:
$ sqlplus system/
e) adruncts.sql will display the disk space needed for adcrtbsp.sql
to complete successfully.
f) adruncts.sql will run adcrtbsp.sql, and the results will be
spooled to adcrtbsp.log in the current directory. Review the log
file to make sure no errors were reported.
Applying this patch
This patch must be applied on the admin server node before it is applied on any
other application tier server node, or else it will fail.
Once all required prerequisite manual tasks have been performed, use AutoPatch
to apply the following unified driver in normal mode:
u3180164.drv
Applying the Release 11.5.10 Maintenance Pack:
a) Shut down application tier server processes:
Shut down all application tier server processes or services except for the database and the Oracle Net listener for the database.
b) Apply the maintenance pack:
Use AutoPatch to apply the u3480000.drv driver .
Note:
If you have a multi-node system, you must apply the driver on the administration server node first. Then, apply all other application tier server nodes, in any order.
While applying maintenance pack we got the following Errors:
Error1:unable to create INITIAL extent for segment in tablespace 'IGFX'
SOLUTION:
sql> select name,bytes/(1024*1024) from v$datafile where name like '%igf%';
sql>alter database datafile '/d02/oraofdb/ofdbdata/igfx01.dbf' autoextend on next 1 M maxsize 150 M;
Then restart the worker by using adctrl utility.
started sucssesfully
Error 2:ORA 1658 -unable to create INITIAL extent for segment in tablespace 'BISD'
Solution:
sql>alter database datafile '/d02/oraofdb/ofdbdata/bisd01.dbf' autoextend on next 1m maxsize 250m;
Then restart the worker by using adctrl utility.
started sucssesfully
Post Upgrade Steps:
After finishing Maintainance Pack i got the Error ,while starting the application services
adalnctl.sh: exiting with status 127
Cause:
the program lsnrctl executable is not sucessfully created or missing..
Solution:
I refered the Doc ID-299810.1 and apply the 3830807 patch.
excellent
ReplyDeletegr8 explaination
ReplyDelete