Showing posts with label Patch. Show all posts
Showing posts with label Patch. Show all posts

Applying Developer patchset 18 and ATG RUP 6

ENVIRONMENT

OS: AIX Version 5.3
DB: 10g (10.2.0.1.0)
APPS: 11i (11.5.10.2)


1.0.0 Apply AD.I.6 Minipack

Apply patch 6502082 using adpatch

Instructions

1. Before Applying This 5985992 Patch

Perform the steps listed below:

1.2 From the location where this patch was unzipped, change directory to fnd/patch/115/bin .

1.3 Run the Validation script as follows:

------------------------------------------
NOTE:

Ensure that your current working directory is
[patch unzipped location]/fnd/patch/115/bin

------------------------------------------ on Unix:

./txkprepatchcheck.pl -script=ValidateRollup
-outfile=$APPLTMP/txkValidateRollup.html
-appspass=


1.4 Review the report generated by the validation script

2. How To Apply This Patch

This patch contains the following driver file to be applied with
AutoPatch: u5985992.drv (This is the unified driver).

2.1 After Applying this Patch Run Autoconfig

2.2 Update the RDBMS ORACLE_HOME file system with the AutoConfig files by
performing the following steps:

2.2.1 On the Application Tier (as the APPLMGR user):
2.2.1.1 Source the environment file.
2.2.1.2 Create the appsutil.zip file by executing:
$ADPERLPRG $AD_TOP/bin/admkappsutil.pl

This will create appsutil.zip in $APPL_TOP/admin/out .

2.2.2 On the Database Tier (as the ORACLE user):
2.2.2.1 Copy or FTP the appsutil.zip file to the
2.2.2.2 cd
2.2.2.3 unzip -o appsutil.zip
2.2.2.4 Run AutoConfig by executing:

2.3 Apply 11.5.10 INTEROP PATCH FOR 10GR2
Apply patch 4653225 using adpatch

Apply patch 4948577(patchset 18) For Oracle Developer

1.1 Apply Developer patchset 18

1. Apply patch 4948577 to 8.0.6 Home on app and admin tiers

Note:
Before moving ahead with patch application ensure following:

All processes, running out of the ORACLE_HOME being patched, are shutdown cleanly.
$PATH includes $ORACLE_HOME/bin and also it points to locations where following executables are present: make, ar, ld, and nm.
$ORACLE_HOME should point to 806 Oracle Home.
$ORACLE_HOME and $JDK_HOME environment variables are set.
Set JDK_HOME to the JDK directory (JDK 1.3.1 or above).
For example, if you have JDK version 1.3.1 installed under /usr/local/packages/jdk1.3.1 directory, then set JDK_HOME to /usr/local/packages/jdk1.3.1/jdk
Make sure to backup the current /etc/oraInst.loc file.
Point the inventory location to the correct path in the oraInst.loc with the directory having the required inventory information


Reference:

Unzip the patch in 8.0.6 $ORACLE_HOME. .
Run the install script contained in the patch:
cd $ORACLE_HOME/developer6i_patch18
./patch_install.sh 2>&1 tee patch_install_p18.log
Check patch_install_p18.log for errors.


2. Relink Procedure Builder

Reference:
cd $ORACLE_HOME/procbuilder60/lib;
make -f ins_procbuilder.mk install

3. Relink Forms
Reference:
cd $ORACLE_HOME/forms60/lib;
make -f ins_forms60w.mk install

4. Relink Graphics
Reference:
cd $ORACLE_HOME/graphics60/lib;
make -f ins_graphics60w.mk install


5. Relink Reports
Reference:
Reports has both link-time and run-time dependency with libjava.so, so you need to append $ORACLE_HOME/network/jre11/lib/sparc/native_threads in $LD_LIBRARY_PATH before linking Reports. The same $LD_LIBRARY_PATH should be used at run-time.
cd $ORACLE_HOME/reports60/lib;
make -f ins_reports60w.mk install

1.2 Install Additional patches for Developer6i patchset 18

1.2.1 Apply patch 5713544

Unzip the patch. Change the directory to where the patch was unzipped.
cd 5713544
If you don't have genshlib in $ORACLE_HOME/bin directory then copy this file over there.
cp genshlib $ORACLE_HOME/bin
sh patch.sh


1.2.2 Apply patch 4261542

Copy the patch file to 6i Oracle Home
cd $ORACLE_HOME
Unzip the patch
Backup the Forms class files, i.e.$ORACLE_HOME/forms60/java/oracle/forms/handler/AlertDialog.class
%cp -r $ORACLE_HOME/forms60/java/oracle/forms/handler/AlertDialog.class
$ORACLE_HOME/forms60/java/oracle/forms/handler/AlertDialog.class.PRE_BUG4261542
%cp -r $ORACLE_HOME/forms60/java/oracle/forms/engine/Main.class
$ORACLE_HOME/forms60/java/oracle/forms/engine/Main.class.PRE_BUG4261542

Copy this file into ORACLE_HOME/forms60/java/oracle/forms/engine
%cd $ORACLE_HOME/4261542/oracle/forms/engine
%cp Main.class $ORACLE_HOME/forms60/java/oracle/forms/engine/Main.class
%cd $ORACLE_HOME/4261542/oracle/forms/handler
%cp AlertDialog.class $ORACLE_HOME/forms60/java/oracle/forms/handler/AlertDialog.class


1.2.3 Apply patch 5216496

Copy the zip in $ORACLE_HOME and Unzip the zip file. This will unzip into 5216496 folder.
• If you don't have genshlib in $ORACLE_HOME/bin directory then copy this file over there.
cp genshlib $ORACLE_HOME/bin
• Copy your original libraries in case you ever need it:
cd $ORACLE_HOME/lib
cp libiff.a libiff.a.ORG
cp libiff.so.0 libiff.so.0.ORG
cp libiffw.a libiffw.a.ORG
cp libiffw.so.0 libiffw.so.0.ORG
• Archive .o into iwf and iwfw library
cd $ORACLE_HOME/5216496/opt
ar -rv $ORACLE_HOME/lib/libiff.a ifzprs.o
cd $ORACLE_HOME/5216496/optweb
ar -rv $ORACLE_HOME/lib/libiffw.a ifzprs.o
• Generate All *.so's
cd $ORACLE_HOME/lib
$ORACLE_HOME/bin/genshlib iffw 0
$ORACLE_HOME/bin/genshlib iff 0
• Generate forms executables
cd $ORACLE_HOME/forms60/lib
make -f cus_forms60w.mk install

1.2.4 Apply patch 5753922
Unzip Patch file into 6i Oracle Home
cd 5753922
sh patch.sh

1.2.5 Apply patch 6195758

Unzip the patch into 6i Oracle Home.
cd $ORACLE_HOME
unzip p6195758_600_GENERIC.zip

Unzip the java class files and regenerate your JAR files

Backup the Forms class files,

%cp -r $ORACLE_HOME/forms60/java/oracle/forms/handler/UICommon.class
$ORACLE_HOME/forms60/java/oracle/forms/handler/UICommon.class.PRE_BUG6195758

%cp -r $ORACLE_HOME/forms60/java/oracle/forms/handler/ComponentItem.class
$ORACLE_HOME/forms60/java/oracle/forms/handler/ComponentItem.class.PRE_BUG6195758

Inside folder 6195758 in step-2 has class files in oracle\forms\handler directory. Copy this file into ORACLE_HOME/forms60/java/oracle/forms/handler

cd $ORACLE_HOME/6195758/oracle/forms/handler
cp UICommon.class $ORACLE_HOME/forms60/java/oracle/forms/handler/UICommon.class
%cp ComponentItem.class $ORACLE_HOME/forms60/java/oracle/forms/handler/ComponentItem.class

1.2.6 Apply Patch 5938515

Unzip Patch file in 6i Oracle Home
cd 5938515
sh patch.sh

1.3 Apply Forms Interoperability Patch

Apply patch 4888294 using adpatch

1.3.1 APPLICATIONS INTEROPERABILITY PATCH

Apply patch 3830807 using adpatch

1.3.2 UNABLE TO RELINK LIBIFJAPI60.SO IN RHAS3.0

Apply patch 4586086 using adpatch


1.4 Generate JAR Files

Generate JAR files using adadmin

1.5 Apply Security Fixes to Developer 6i
1.5.1 Apply patch 5687261 to forms server


Unzip patch in 6i oracle home
cd 5687261
sh patch.sh 2>&1 tee patch.log
Please inspect patch.log for any errors

1.5.2 Apply patch 5686997
Unzip the patch in 6i Oracle Home
cd 5686997
sh patch.sh 2>&1 tee patch.log
Please inspect patch.log for any errors.

1.5.3 Apply patch 5078711

• Make sure that all processes running from the ORACLE_HOME being patched are shutdown before installing this patch.
• Ensure that ORACLE_HOME is set.
• Set JDK_HOME to the JDK directory (JDK 1.3.1 or later).
• Ensure $ORACLE_HOME/bin is included in your PATH environment variable, and also ensure that the following executables must be present in the $PATH: make, ar, ld, nm
• Set your current directory to the directory where the patch is located and then run the installcpu.sh script by entering the following UNIX command:
sh installcpu.sh
Inspect the following install log file for any errors:
installcpu.sh log file $ORACLE_HOME/cpu/5078711/install.log

***********************************



Apply ATG_PF RUP6

Apply Technology Stack Patch

CPUApr2008 6831988 EBS11i:Technology Stack (TXK) Components For Critical Patch Update April 2008

1.6 Apply Pre-Req Patches

1.6.1 Apply AD.I.6 Minipack
Apply patch 6502082 using adpatch
1.6.2 Post AD.I.6 patch Tasks

1.6.2.1 Grant privileges and create PL/SQL profiler objects
Run the adgrants.sql script as a user that can connect as SYSDBA to grant privileges to selected SYS objects and create PL/SQL profiler objects.

• Create $ORACLE_HOME/appsutil/admin on the database server.
• Copy adgrants.sql from $APPL_TOP/admin to $ORACLE_HOME/appsutil/admin.
• Set the environment to point to ORACLE_HOME on the database server.
• Run following commands
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql
1.6.2.2 Run Adconfig
Run adconfig to instantiate the templates used by AD Utilities
1.6.2.3 Perform Adadmin Tasks
• Regenerate JAR files using adadmin.
• Update current view snapshot

1.7 Apply ATG_PF RUP6

1.7.1 Apply pre-req patches
Apply following pre-req patches

1.7.1.1 Apply patch 5989593

Apply patch using adpatch
Create $ORACLE_HOME/appsutil/admin on the database server.
Copy adgrants.sql (UNIX) from the patchtop(5989593)/admin directory to
$ORACLE_HOME/appsutil/admin.
Set the environment to point to ORACLE_HOME on the database server.
Use SQL*Plus to run the script:

$ sqlplus /nolog
SQL> connect / as sysdba
SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql

1.7.1.2 Apply patch 4291053

Apply patch using adpatch
Run adadmin and
Compile APPS Schema
Compile Flexfield data in AOL Tables

1.7.1.3 Apply patch 3218526 – BNE.D

Apply patch using adpatch
Run adadmin and
Compile APPS Schema
Compile Flexfield data in AOL Tables

Perform following post patch steps

Once you have successfully applied minipack 11i.BNE.D, you must complete these additional product-specific tasks. This section describes these tasks.

 The Web server must be restarted after the successful application of the Patch Set.
 Review the list of profile options in the Implementation and User Documentation specified in the Additional Product Information section.
 Review the seeded form functions, menu, and responsibility in the Implementation and User Documentation specified in the Additional Product Information section. Give Oracle Application Users access to Web ADI form functions. Simply assigning the seeded Desktop Integration Responsibility to a user can do this. See the Oracle Applications System Administrator's Guide for more information on giving users access to form functions on the Personal Home Page.
 If your site is using the General Ledger - Journals Integrator:
o Make sure the GL: Set of Books Name profile option is set for all user profiles.
o Assure that at least one of the following form functions is associated with the menu that contains the form function they use to access Web ADI: Enter Budget Journals, Enter Journals, Enter Encumbrances, Import Journals, and Create Document.
 After BNE.D has been applied, then apply the latest ATG RUP patchset - currently that is ATG RUP6. All of the Web ADI fixes that have been made on top of BNE.D have been rolled up in the the latest ATG RUP patchset. In order to get these latest updates, you should apply the latest ATG RUP patch 6. Reference Patch 5903765 11i.ATG_PF.H. RUP6 and Note 444524.1 for more information
 Sites using Internal Controls Manager need to apply Patch 4483674 after applying BNE.D Minipack.
 Sites using Financial Intelligence need to apply Patch 3857216 after applying BNE.D Minipack.
 Sites using HRMS need to apply Patch 4199321 after applying BNE.D Minipack. Please consult the HRMS Metalink page for any additional patches which may also need to be applied.

1.7.1.4 Apply patch 3761838 – FRM.G
1.7.1.5 Apply patch 4206794 – FRM.H


Apply patch 4206794 using adpatch
Perform following adadmin task after successful application of patch
• Generate message files
• Compile APPS schema(s)
• Compile flexfield data
• Recreate grants and synonyms for APPS schema(s)
• Gather schema statistics

1.7.2 Run the technology stack validation utility

• Source the environment logged in as applmgr
• Ensure that APPLRGF environment is set, if not then set it to the value of APPLTMP
• From the location where this patch(ATG_PF>RUP6) was unzipped, change directory to fnd/patch/115/bin.
• Run the tech stack validation utility as follows:
• ./txkprepatchcheck.pl -script=ValidateRollup
-outfile=$APPLTMP/txkValidateRollup.html
-appspass=
• Check the report filegenerated by this utility for any actions required to perform

1.7.3 Apply ATG_PF.RUP6 patch using adpatch.
Apply patch 5903765 using adpatch
1.7.4 Post ATG_PF.RUP6 steps
Apply following patches using adpatch
3865683


Complete Adadmin Tasks
Complete following adadmin tasks
• Generate message files
• Compile apps schema
• Compile flexfields
• Compile menus
• Run “Gather Schema Statistics” concurrent program

How To Use AD Merge Patch

Create Source and destination directory
Copy all the patche to source directory
and run the below scripts
admrgpch -s /home/applmgr/patch10g/source -d /home/applmgr/patch10g/dest -merge_name ramesh

Executing the merge of the patch drivers -- Processing patch: /home/applmgr/patch10g/source/4888294 -- Done processing patch: /home/applmgr/patch10g/source/4888294
-- Processing patch: /home/applmgr/patch10g/source/4653225 -- Done processing patch: /home/applmgr/patch10g/source/4653225
-- Processing patch: /home/applmgr/patch10g/source/5985992 -- Done processing patch: /home/applmgr/patch10g/source/5985992
-- Processing patch: /home/applmgr/patch10g/source/6502082 -- Done processing patch: /home/applmgr/patch10g/source/6502082

Copying files...
5% complete. Copied 98 files of 1942...
10% complete. Copied 195 files of 1942...
15% complete. Copied 292 files of 1942...
20% complete. Copied 389 files of 1942...
25% complete. Copied 486 files of 1942...
30% complete. Copied 583 files of 1942...
35% complete. Copied 680 files of 1942...
40% complete. Copied 777 files of 1942...
45% complete. Copied 874 files of 1942...
50% complete. Copied 971 files of 1942...
55% complete. Copied 1069 files of 1942...
60% complete. Copied 1166 files of 1942...
65% complete. Copied 1263 files of 1942...
70% complete. Copied 1360 files of 1942...
75% complete. Copied 1457 files of 1942...
80% complete. Copied 1554 files of 1942...
85% complete. Copied 1651 files of 1942...
90% complete. Copied 1748 files of 1942...
95% complete. Copied 1845 files of 1942...
100% complete. Copied 1942 files of 1942...

Character-set converting files...
4 unified drivers merged.
Patch merge completed successfully
Please check the log file at ./admrgpch.log.

Developer 6i Patch Patch 18*

Download the below Patches for developer 6i Patch set.



===========================================================

6502082 - done - AD.I.6
5985992 - done - TXK AUTOCONFIG ROLLUP PATCH Q (JUL/AUG 2007)

3453499 - already applied

4653225 - done - 11.5.10 INTEROP PATCH FOR 10GR2

==============================================================
4948577 - done - Developer 6i Patch Patch 18*

4888294 - done - Apps Interop Patch

3830807 - done - APPLICATIONS INTEROPERABILITY PATCH

4586086 - done - UNABLE TO RELINK LIBIFJAPI60.SO IN RHAS3.0

Download Additional Developer 6i Patches
5713544 - done
4261542 - done
5216496 - done
5753922 - done
6195758 - done
5938515 - done
================================================================

Apply this patch 5985992

From the location where this patch was unzipped, change directory
to fnd/patch/115/bin .

on Unix:

./txkprepatchcheck.pl -script=ValidateRollup -outfile=$APPLTMP/txkValidateRollup.html -appspass=apps


[applmgr@sys43 bin]$ ./txkprepatchcheck.pl -script=ValidateRollup -outfile=$APPLTMP/txkValidateRollup.html -appspass=apps
*** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS
*** STDOUT = /oracle/app/apps/testcomn/rgf/TEST_sys43/TXK/txkValidateRollup_Fri_Apr_11_21_21_24_2008_stdout.log
Reportfile /oracle/app/apps/testcomn/temp/txkValidateRollup.html generated successfully.




On the Application Tier (as the APPLMGR user):

Source the environment file.

Create the appsutil.zip file by executing:

$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 or FTP the appsutil.zip file to the


cd
unzip -o appsutil.zip

Run AutoConfig by executing:
/appsutil/scripts//
adautocfg.sh

==================================================================

Forms & Reports 6i Patch 18 for Linux



Set your ORACLE_HOME.
If you are going to apply this patch on top of an iAS install:
Set ORACLE_HOME to /6iserver
Prepend /6iserver/bin to the *beginning* of PATH
Prepend /6iserver/lib to the *beginning* of LD_LIBRARY_PATH
==========================================================
[applmgr@sys43 patch10g]$ export ORACLE_HOME=/oracle/app/apps/testora/iAS/6iserver
[applmgr@sys43 patch10g]$ export LD_LIBRARY_PATH=/oracle/app/apps/testora/iAS/6iserver/lib:$LD_LIBRARY_PATH
[applmgr@sys43 patch10g]$ export PATH=/oracle/app/apps/testora/iAS/6iserver/bin:$PATH


[applmgr@sys43 6iserver]$ pwd
/oracle/app/apps/testora/iAS/6iserver
=============================================
Copy the files in this patch to your $ORACLE_HOME
[applmgr@sys43 developer6i_patch18]$ echo $ORACLE_HOME
/oracle/app/apps/testora/iAS/6iserver
[applmgr@sys43 6iserver]$ unzip p4948577_600_LINUX.zip

ls -ltr
drwxr-xr-x 6 applmgr oinstall 4096 Jan 13 2006 developer6i_patch18

[applmgr@sys43 developer6i_patch18]$ pwd
/oracle/app/apps/testora/iAS/6iserver/developer6i_patch18
Run the install script contained in the patch:
cd $ORACLE_HOME/developer6i_patch18
./patch_install.sh 2>&1 | tee patch_install_p18.log (ksh)
./patch_install.sh |& tee patch_install_p18.log (csh)
================================================================
[applmgr@sys43 developer6i_patch18]$ ./patch_install.sh 2>&1 | tee patch_install_p18.log

Patch can be deinstalled by using /oracle/app/apps/testora/iAS/6iserver/developer6i_patch18/patch_deinstall.sh script
===============================================================
Check patch_install_p18.log for errors
Relink Procedure Builder, Forms, Graphics and Reports:
cd $ORACLE_HOME/procbuilder60/lib; make -f ins_procbuilder.mk install
cd $ORACLE_HOME/forms60/lib; make -f ins_forms60w.mk install
cd $ORACLE_HOME/graphics60/lib; make -f ins_graphics60w.mk install

============================================================
[applmgr@sys43 developer6i_patch18]$ cd $ORACLE_HOME/procbuilder60/lib
[applmgr@sys43 lib]$ make -f ins_procbuilder.mk install

[applmgr@sys43 lib]$ cd $ORACLE_HOME/forms60/lib
[applmgr@sys43 lib]$ make -f ins_forms60w.mk install

[applmgr@sys43 lib]$ cd $ORACLE_HOME/graphics60/lib
[applmgr@sys43 lib]$ make -f ins_graphics60w.mk install

========================================================

Reports has both link-time and run-time dependency with libjava.so so you need to append either one of:
$ORACLE_HOME/network/jre11/lib/linux/native_threads
$ORACLE_HOME/network/jre11/lib/i686/native_threads
in $LD_LIBRARY_PATH before linking Reports.
Please check your files under $ORACLE_HOME/network/jre11/lib to see which one of the above is appropriate on your system. The same $LD_LIBRARY_PATH should be used at run-time.
cd $ORACLE_HOME/reports60/lib; make -f ins_reports60w.mk install


======================================================
[applmgr@sys43 lib]$ cd $ORACLE_HOME/network/jre11/lib/i686/
[applmgr@sys43 i686]$ pwd
/oracle/app/apps/testora/iAS/6iserver/network/jre11/lib/i686
[applmgr@sys43 i686]$ ls -ls native_threads
total 4940
2552 -rwxr-xr-x 1 applmgr oinstall 2606042 Jun 20 2001 libawt.so
1376 -rwxr-xr-x 1 applmgr oinstall 1404357 Jun 20 2001 libjava.so
312 -rwxr-xr-x 1 applmgr oinstall 313893 Jun 20 2001 libjpeg_sun.so
164 -rwxr-xr-x 1 applmgr oinstall 160561 Jun 20 2001 libmath.so
88 -rwxr-xr-x 1 applmgr oinstall 84707 Jun 20 2001 libmmedia.so
156 -rwxr-xr-x 1 applmgr oinstall 151672 Jun 20 2001 libnet.so
88 -rwxr-xr-x 1 applmgr oinstall 85802 Jun 20 2001 libsysresource.so
204 -rwxr-xr-x 1 applmgr oinstall 203482 Jun 20 2001 libzip.so


[applmgr@sys43 i686]$ export LD_LIBRARY_PATH=$ORACLE_HOME/network/jre11/lib:$LD_LIBRARY_PATH
[applmgr@sys43 i686]$ cd $ORACLE_HOME/reports60/lib
[applmgr@sys43 lib]$ make -f ins_reports60w.mk install
=======================================================


[applmgr@sys43 bin]$ pwd
/oracle/app/apps/testora/iAS/6iserver/developer6i_patch18/bin
-rwxr-xr-x 1 applmgr oinstall 2811 Dec 12 2005 genshlib

Copy this file genshlib to /oracle/app/apps/testora/iAS/6iserver/bin
[applmgr@sys43 bin]$ cp genshlib genshlib.bak_Apr12
[applmgr@sys43 bin]$ pwd
/oracle/app/apps/testora/iAS/6iserver/bin
[applmgr@sys43 bin]$ cp -b genshlib /oracle/app/apps/testora/iAS/6iserver/bin

============================================================


unzip p3830807_8063_LINUX.zip

cd 3830807

chmod u+x patch.sh

export LD_LIBRARY_PATH=/oracle/app/apps/testora/8.0.6/network/jre11/lib:$LD_LIBRARY_PATH

./patch.sh

================================================================================

cd $ORACLE_HOME
mkdir patch
cd patch

unzip p4586086_600_LINUX.zip


cd $ORACLE_HOME/forms60/lib

[applmgr@sys43 lib]$ ls -lrt env_forms60.mk
-rw-r--r-- 1 applmgr oinstall 28454 Dec 22 2005 env_forms60.mk

mv env_forms60.mk env_forms60.mk.PRE_BUG4586086


cp $ORACLE_HOME/patch/bug4586086/env_forms60.mk $ORACLE_HOME/forms60/lib

cd $ORACLE_HOME/forms60/lib
make -f cus_forms60w.mk libso_install


adrelink.sh force=y "fnd f60webmx"


=============================================================

cd 5713544
sh patch.sh

E.g. to relink f60webmx for Oracle Applications
adrelink.sh force=y "fnd f60webmx"

===============================================================


1. Stop your web listeners and Forms Server.

2. Make a patch directory within your 6i ORACLE_HOME and unzip

cd $ORACLE_HOME
[applmgr@sys43 6iserver]$ cp p4261542_600_GENERIC.zip $ORACLE_HOME
unzip p4261542_600_GENERIC.zip


[Part 2] Unzip the java class files and regenerate your JAR files

3. Backup the Forms class files, i.e.$ORACLE_HOME/forms60/java/oracle/forms/handler/AlertDialog.class

[applmgr@sys43 4261542]$ cd $ORACLE_HOME/forms60/java/oracle/forms/handler/
[applmgr@sys43 handler]$ ls -ls AlertDialog.class
8 -rw-rw-r-- 1 applmgr oinstall 6673 Dec 21 2005 AlertDialog.class

[applmgr@sys43 handler]$ mv AlertDialog.class AlertDialog.class.bak

[applmgr@sys43 handler]$ cd $ORACLE_HOME/forms60/java/oracle/forms/engine/
[applmgr@sys43 engine]$ ls -ls Main.class
24 -rw-rw-r-- 1 applmgr oinstall 20545 Dec 21 2005 Main.class

[applmgr@sys43 engine]$ mv Main.class Main.class.bak




4. Inside folder 4261542 in step-2 has class files in oracle\forms\engine directory.
Copy this file into ORACLE_HOME/forms60/java/oracle/forms/engine

[applmgr@sys43 engine]$ cd $ORACLE_HOME/4261542/oracle/forms/engine
[applmgr@sys43 engine]$ cp Main.class $ORACLE_HOME/forms60/java/oracle/forms/engine/Main.class
[applmgr@sys43 engine]$ cd $ORACLE_HOME/4261542/oracle/forms/handler
[applmgr@sys43 handler]$ cp AlertDialog.class $ORACLE_HOME/forms60/java/oracle/forms/handler/AlertDialog.class


5. Generate JAR Files use adadmin

=================================

cd 5216496
sh patch.sh
=================================

[applmgr@sys43 6iserver]$ cp p6195758_60827_GENERIC.zip $ORACLE_HOME

[applmgr@sys43 6iserver]$ unzip p6195758_60827_GENERIC.zip

Backup the Forms class files,


[applmgr@sys43 handler]$ cd $ORACLE_HOME/forms60/java/oracle/forms/handler/
[applmgr@sys43 handler]$ mv UICommon.class UICommon.class.bak
[applmgr@sys43 handler]$ cd $ORACLE_HOME/forms60/java/oracle/forms/handler/
[applmgr@sys43 handler]$ mv ComponentItem.class ComponentItem.class.bak

Inside folder 6195758 in step-2 has class files in oracle\forms\handler directory.
Copy this file into ORACLE_HOME/forms60/java/oracle/forms/handler


[applmgr@sys43 handler]$ cd $ORACLE_HOME/6195758/oracle/forms/handler
[applmgr@sys43 handler]$ cp UICommon.class $ORACLE_HOME/forms60/java/oracle/forms/handler/UICommon.class
[applmgr@sys43 handler]$ cp ComponentItem.class $ORACLE_HOME/forms60/java/oracle/forms/handler/ComponentItem.class

====================================

cd 5938515
sh patch.sh

adrelink.sh force=y "fnd f60webmx"

========================================


cd 5753922
sh patch.sh

adrelink.sh force=y "fnd f60webmx"

=======================================


How to find forms version in patch set


$ORACLE_HOME/bin/f60gen help=y
Forms 6.0 (Form Compiler) Version 6.0.8.27.0 (Production)

Metalik id :125767.1

6.0.8.27.0 ===> Patch 18




Pre-Upgrade Step:


select banner from v$version;

SELECT product_group_id GroupID, product_group_name GroupName,release_name Release,product_group_type GroupType, argument1 FROM fnd_product_groups;

select count(*) from ad_bugs where bug_number = '5985992';


patch 4653225

Check the developer 6i Patch set.

Metalink Note 125767.1


Developer 6i patchset 18 (4948577)

How to Apply an 11i Patch When adpatch is Already Running

1. Using the adctrl utility, shutdown the workers.

a. adctrl
b. Select option 3 "Tell worker to shutdown/quit"

2. Backup the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema

a. sqlplus applsys/
b. create table fnd_Install_processes_back
as select * from fnd_Install_processes;
c. The 2 tables should have the same number of records.
select count(*) from fnd_Install_processes_back;
select count(*) from fnd_Install_processes;

3. Backup the AD_DEFERRED_JOBS table.

a. sqlplus applsys/
b. create table AD_DEFERRED_JOBS_back
as select * from AD_DEFERRED_JOBS;
c. The 2 tables should have the same number of records.
select count(*) from AD_DEFERRED_JOBS_back;
select count(*) from AD_DEFERRED_JOBS;

4. Backup the .rf9 files located in $APPL_TOP/admin//restart directory.

At this point, the adpatch session should have ended and the cursor should
be back at the Unix prompt.
a. cd $APPL_TOP/admin/
b. mv restart restart_back
c. mkdir restart

5. Drop the FND_INSTALL_PROCESSES table and the AD_DEFERRED_JOBS table.

a. sqlplus applsys/
b. drop table FND_INSTALL_PROCESSES;
c. drop table AD_DEFERRED_JOBS;

6. Apply the new patch.

7. Restore the .rf9 files located in $APPL_TOP/admin//restart_back
directory.


a. cd $APPL_TOP/admin/
b. mv restart restart_
c. mv restart_back restart

8. Restore the FND_INSTALL_PROCESSES table which is owned by the APPLSYS
schema.


a. sqlplus applsys/
b. create table fnd_Install_processes
as select * from fnd_Install_processes_back;
c. The 2 tables should have the same number of records.
select count(*) from fnd_Install_processes;
select count(*) from fnd_Install_processes_back;

9. Restore the AD_DEFERRED_JOBS table.

a. sqlplus applsys/
b. create table AD_DEFERRED_JOBS
as select * from AD_DEFERRED_JOBS_back;
c. The 2 tables should have the same number of records.
select count(*) from AD_DEFERRED_JOBS_back;
select count(*) from AD_DEFERRED_JOBS;

10. Re-create synonyms

a. sqlplus apps/apps
b. create synonym AD_DEFERRED_JOBS for APPLSYS.AD_DEFERRED_JOBS;
c. create synonym FND_INSTALL_PROCESSES FOR APPLSYS.FND_INSTALL_PROCESSES;

11. Start adpatch, it will resume where it stopped previously.

Note:175485.1

PLS-00302: component 'IS_PATCH_APPLIED2' must be declared

while applying the patch 6502082

AutoPatch error:Error while executing statement
AutoPatch error:ORA-06550: line 3, column 10:
PLS-00302: component 'IS_PATCH_APPLIED2' must be declared
ORA-06550: line 3, column 1:PL/SQL: Statement ignored
AutoPatch error:--------adppdepIsPatchApplied() returned FALSE
See messages above for details.

Solutions

Go to Bellow path and compile the adphpchb.pls objects.
Connect Apps login

$AD_TOP/patch/115/sql/adphpchb.pls
After compile this objects, Then try to apply the patch.

Current Patchset Comparison Utility - patchsets.sh

You can find your apps pactch set level.if you want more information click below URL
Download patchesets.sh
ftp://ftp.oracle.com/support/outgoing/PATCHSET_COMPARE_TOOL/patchsets.sh

AD Patch

Applying a patch updates your existing system in various ways, from adding a new
feature or product to improving system performance.

patches are applied for a number of reasons, including:

■ Fixing an existing issue
■ Adding a new feature or functionality
■ Updating to a higher maintenance level
■ Applying the latest product enhancements
■ Providing interoperability to new technology stacks
■ Determining the source of an issue
■ Applying online help

Depending on the type of patch, it may update the file system, or the database, or
both.

Unified Driver File
The unified driver, named u.drv, contains the commands necessary to
change files and database objects, and to generate new objects. It contains copy,
database, and generate portions and performs the copy, database, and generate actions
in the stated order. You typically run the unified driver on all APPL_TOPs. AutoPatch
runs only the actions that are required for the current APPL_TOP.

C,D and G Driver File
C – copy driver
D – database driver
G – forms and reports generation driver

Command Line Patching Utilities
You run the following utilities from the command line.

AutoPatch
AutoPatch is the utility used to apply all patches to the Oracle Applications file system or database.

AD Merge Patch
When you apply patches individually, you must perform patching tasks multiple
times. For example, for every individual patch there may be duplicate link and
generate processes. AD Merge Patch merges multiple patches into a single patch so
that the required patching tasks and processes are performed only once.

i.e. admrgpch -s ./source -d ./target -merge_name merged001

AutoPatch

Use AutoPatch to apply patches to the Oracle Applications file system or database. It
gathers necessary information about your system through a series of prompts. When
you have completed the prompts, AutoPatch performs all the tasks required to apply
the patch, including the following:
■ Reads patch metadata to determine patch dependencies and requirements.
■ Uploads patch information from a prior patch session to the database (if needed).
■ Reads and validates the patch driver file and reads the product driver files.
■ Compares version numbers of object modules from the product libraries and
version numbers of the existing files against the patch files.
■ Backs up all existing files that will be changed by the patch.
■ Copies files.
■ Archives files in libraries.
■ Relinks executables.
■ Generates forms, reports, message, graphics, and Java archive (JAR) files.
■ Compiles JSP files and invalid database objects.
■ Updates database objects.
■ Runs AutoConfig to update configuration files, if any template files are introduced
or updated by the patch.
■ Saves patch information to the database.
AutoPatch takes no action if a patch contains no new updates to files or database
objects in your system. If AutoPatch detects that there is a previously failed AutoPatch session, it will attempt to recover that session.Preparing your System for Patching.

Before you begin a patching session, there are some important tasks you need to
complete.

Enable Maintenance Mode

Before you initiate an AutoPatch session, you should enable maintenance mode and Shutdown concurrent manager. During a maintenance mode downtime, user login is restricted. Users are redirected to a system downtime URL, which informs them that the maintenance session is in progress.

To enable or disable maintenance mode, use the Change Maintenance Mode menu in
AD Administration.

Shut Down Services
If you are applying a patch that updates or relinks files, shut down the corresponding concurrent manager, Web server listeners.

Log File Description
adpatch.log main AutoPatch log file (default name)
adpatch.lgi for AutoPatch informational messages (default name)
adrelink.log for relinking

Command Line Arguments
You can direct the way the AutoPatch operates by adding modifiers to the AutoPatch
start command. These modifiers may be in the form of arguments or options.

$ adpatch logfile=test.log
You can enter more than one token=value argument on a single command line by
separating them with one blank space as in the following AutoPatch command.

$ adpatch printdebug=y flags=hidepw
In some cases, you can include more than one value for a token. In this case, separatethe values with commas.
$ adpatch flags=nohidepw,trace
Comma-separated lists must not contain blank spaces. For example, this command is
not valid:
$ adpatch flags=nohidepw, trace
The following arguments are specific to AutoPatch and can be used to modify and
refine its behavior.

AutoPatch Options
The options= argument is used to pass generic options to AutoPatch. It takes the form
of a comma-separated list. Enter one option or a comma-separated list of options. For
example, options=nocopyportion,nogenerateportion. Do not include a space after the

Option Description
autoconfig Purpose: Tells AutoPatch to run AutoConfig automatically.
Default: autoconfig

Use options=noautoconfig if you are applying a number of patches in
sequence and want to run AutoConfig once, after applying the last patch of
the sequence.

Default: checkfile
Use options=nocheckfile to turn off the checkfile feature.

Default: compiledb for standard patches. nocompiledb for standard patch
translations, documentation patches, and documentation patch translations.
Use options=nocompiledb to save time when multiple non-merged patches are
applied in a maintenance window.

Default: compilejsp for standard patches. nocompilejsp for standard patch
translations, documentation patches, and documentation patch translations.
Use options=nocompilejsp to save time when multiple non-merged patches
are applied in a maintenance window.

Default: copyportion
Use options=nocopyportion to tell AutoPatch not to perform copy actions of
the driver.

Default: databaseportion
Use options=nodatabaseportion to tell AutoPatch not to perform database
actions. of the driver

Default: generateportion
Use options=nogenerateportion to tell AutoPatch not to perform generate
actions of the driver.

Default: nohotpatch
integrity Purpose: Tells AutoPatch whether to verify that the version of each file
referenced in a copy action matches the version present in the patch.

Default: nointegrity
Comments: Using options=nointegrity is safe and avoids some AutoPatch
overhead.

Default: nophtofile
Use options=phtofile to tell AutoPatch not to upload patch history
information to the database.

Interactive or Non-interactive Patching
You can apply patches interactively or non-interactively.

Interactive patching means that you supply basic information that AutoPatch needs by responding to a series of prompts.

Non-interactively substantially reduces the need for user intervention when AutoPatch processes patching tasks. You create a defaults file that contains much of the information you would have supplied at the AutoPatch prompts. Then, when you run AutoPatch, you specify the name of the defaults file, the location of the patch top directory, the name of a driver file, and other parameters on the command line.

Create the defaults file.
Start AutoPatch, using the defaultsfile= argument, and specify the file name and the
path to the defaults file. This creates a defaults file for the current environment.
UNIX:
The file must be under the $APPL_TOP/admin/ directory, where is
the database name (ORACLE_SID/TWO_TASK). For example:

$ adpatch defaultsfile=$APPL_TOP/admin/testdb1/adpatchdef.txt

$ adpatch defaultsfile=$APPL_TOP/admin/testdb1/def.txt logfile=1234567.log \
patchtop=$APPL_TOP/patches/1234567 driver=u1234567.drv workers=3 \
interactive=no

Restarting a Non-interactive AutoPatch Session

When AutoPatch is running non-interactively and encounters an error, it exits to the
operating system and reports a failure. The restart argument is intended specifically
for this circumstance. When AutoPatch sees the restart=yes argument, it assumes that
there is an old session, and expects to find one. If it cannot, it will fail. Do not indicate restart=yes to start a new AutoPatch session.

Complete the following steps:
1. Look through the log files, diagnose the error, and fix it.
2. Use the same command line options that you used initially, but add restart=yes.
UNIX:
$ adpatch defaultsfile=$APPL_TOP/admin/testdb1/def.txt logfile=1234567.log \
patchtop=$APPL_TOP/patches/1234567 driver=u1234567.drv workers=3 \
interactive=no restart=yes
Windows:
C:\> adpatch defaultsfile=%APPL_TOP%\admin\testdb1\def.txt \
logfile=1234567.log patchtop=%APPL_TOP%\patches\1234567 \
driver=u1234567.drv workers=3 interactive=no restart=yes

Abandoning a Non-interactive AutoPatch Session

When you specify interactive=no on the AutoPatch command line, AutoPatch expects
that there is no existing failed session. AutoPatch aborts if it finds restart files from a failed session. Running AutoPatch with the interactive=no and restart=yes command line arguments restarts the previously incomplete session.

To start a completely new AutoPatch session when there is an existing failed session,
specify interactive=no and abandon=yes on the AutoPatch command line. With this
command, AutoPatch deletes the restart files and any leftover database information
from the failed session.

Complete the following steps:
1. Verify that you do not want to restart the previous failed session.
2. Start AutoPatch with the abandon=yes option:
UNIX:
$ adpatch defaultsfile=$APPL_TOP/admin/testdb1/def.txt logfile=7654321.log \
patchtop=$APPL_TOP/patches/7654321 driver=c7654321.drv workers=3 \
interactive=no abandon=yes
Windows:
C:/> adpatch defaultsfile=%APPL_TOP%\admin\testdb1\def.txt \
logfile=7654321.log patchtop=%APPL_TOP%\patches\7654321 \
driver=c7654321.drv workers=3 interactive=no abandon=yes

/* Script to find out Patch level of mini Pack */

Select product_version,patch_level from fnd_product_installations
where patch_level like '%FND%';

I.e.
PATCH_LEVEL

11i.FND.H
11i.AX.I
11i.AK.G
11i.XLA.H
11i.GL.J
11i.FA.O

AD Patches Tables

AD_APPLIED_PATCHES
AD_PATCH_DRIVERS
AD_PATCH_RUNS
AD_APPL_TOPS
AD_RELEASES
AD_FILES
AD_FILE_VERSIONS
AD_PATCH_RUN_BUGS
AD_BUGS
AD_PATCH_COMMON_ACTIONS
AD_PATCH_RUN_BUG_ACTIONS
ad_comprising_patches


Concurrent Manager

FND_CONCURRENT_QUEUES
FND_CONCURRENT_PROGRAMS
FND_CONCURRENT_REQUESTS
FND_CONCURRENT_PROCESSES
FND_CONCURRENT_QUEUE_SIZE


FND Tables

FND_APPL_TOPS
FND_LOGINS
FND_USER
FND_DM_NODES
FND_TNS_ALIASES
FND_NODES
FND_RESPONSIBILITY
FND_DATABASES
FND_UNSUCCESSFUL_LOGINS
FND_LANGUAGES
FND_APPLICATION
FND_PROFILE_OPTION_VALUES


If you want any further clarification, check below metalink documents

Patching Best Practices and Reducing Downtime - Note:225165.1
Oracle Applications Patching FAQ - Note:174436.1
How to Merge Patches Using admrgpch - Note:228779.1

Indis localization Patch Tool

1. perl $JA_TOP/inpatch/indpatch.pl drvr_file=5452893.drv fnd_patchset=F appspwd=apps japwd=ja mode=FCD systempwd=manager logfile=$JA_TOP/$APPLLOG/5452893/5452893.log test=n


2. compile - perl compile_il_apps_obj.pl appspwd=apps
3. sqlplus apps/apps @jai_ap_etds_4353842_mig1_apps.sql
4. sqlplus apps/apps @jai_ap_etds_4353842_mig2_apps.sql



1. perl $JA_TOP/inpatch/indpatch.pl drvr_file=4635814.drv fnd_patchset=F appspwd=apps japwd=ja mode=FCD systempwd=manager logfile=$JA_TOP/$APPLLOG/4635814/4635814.log test=n

sqlplus APPS/ @patch/115/sql/ja_in_util_pkg_s.sql
- sqlplus APPS/ @patch/115/sql/ja_in_util_pkg_b.sql




perl $JA_TOP/inpatch/indpatch.pl drvr_file=5498551.drv fnd_patchset=F appspwd=apps japwd=ja mode=FCD systempwd=oracle logfile=$JA_TOP/$APPLLOG/5498551/5498551.log


perl $JA_TOP/inpatch/indpatch.pl .. (On Unix)
c:/> perl %JA_TOP%\inpatch\indpatch.pl .. (On Windows)