Interoperability Notes Oracle EBS Release 11i with Oracle Database 10.2.0.

4 (Doc ID
1135973.1)

Database upgrade from 9i to 10G:

Section 1: Upgrading an 11i Database to Oracle Database 10g

Release 2 (10.2.0)

Follow the instructions in this section if you have an Oracle E-Business Suite Release
11isystem using Oracle8i Release 3 (8.1.7), Oracle9i Release 1 (9.0.1), Oracle9i Release 2
(9.2.0), or Oracle 10g Release 1 (10.1.0), and you wish to upgrade the database server and
instance to Oracle Database 10g Release 2 (10.2.0).

Note : My Current version of Database 9.2.0.3

Before the Database Installation:

1. Verify software versions

The following software component versions must exist in your environment.

Step 2 : Migrate to Oracle Portal 10g (conditional)

Not applicable

Step 3 : Deregister the current database server (conditional) .

If you plan to change the database port, host, SID, or database name parameter on the
database server, you must also update AutoConfig on the database tier and deregister the
current database server node.

Note 1 :This one also not require we want to maintain same port host SID and
DBA name.

Step 4 : Update application tier context file with new database listener port
number (conditional)
The new 10.2.0 Oracle home uses its own database listener for the database
instance, replacing the current database listener. Use the Context Editor to update
the following variables in the Applications context file on each application tier server
node to reflect the 10.2.0 configuration:

Step 5 :Export OLAP analytical workspaces (conditional)

If your database server node is on the 32-bit Solaris platform, perform detailed steps 1 to 4
of Upgrading OLAP from 32 to 64 bits on My Oracle Support.

Note 1: This step not required for us. There are not using OLAP

Database Installation:

Step 1 : Prepare to create the 10.2.0 Oracle home

The 10.2.0 Oracle home must be installed on the database server node in a different
directory than the current Oracle home.

$cd $ORACLE_HOME

$erpp/erppdb/9.2.0/

Cd ..

$erpp/erppdb/

Mkdir 10.2.0
Step 2 : Install the base 10.2.0 software

Step 3 : Install Oracle Database 10g Products from the 10g Companion CD ..
Note : I have companion software once 10.2. installed I will installed 10g companion CD
as well

Step 4 : Perform 10.2.0.4 patch set pre-installation tasks

On the database server node, as the owner of the Oracle 10g file system and
database instance, unzip and extract the 10.2.0.4 patch set file for your platform.
Read the patch set notes (usually README.html). Make sure you thoroughly
understand the upgrade and patch set installation process before you begin. Check
My Oracle Support or contact Oracle Support Services to determine any known
issues with the patch set and its interoperability with Oracle E-Business Suite.

Perform the tasks in the "Preinstallation Tasks" section of the patch set notes (if they
apply to your system).

Step 5 : Perform 10.2.0.4 patch set installation tasks .

On the database server node, as the owner of the Oracle RDBMS file system and
database instance, perform the tasks in the "Installing the Oracle Database 10g
Patch Set Interactively" section of the patch set notes. Make sure that:

 The ORACLE_HOME environment variable points to the new 10.2.0

Oracle home.
 The PATH environment variable includes $ORACLE_HOME/bin and
the directory where the new perl executable is located (usually
$ORACLE_HOME/perl/bin).
 The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.
 The PERL5LIB environment variable points to the directories where the new
perl libraries are located (usually $ORACLE_HOME/perl/lib/[perl version] and
$ORACLE_HOME/perl/lib/site_perl/[perl version])
 You use the runInstaller (UNIX/Linux) or the setup.exe executable (Windows)
provided in the patch set to run OUI.

Step 6 : Create nls/data/9idata directory

On the database server node, as the owner of the Oracle RDBMS file system and
database instance, run the $ORACLE_HOME/nls/data/old/cr9idata.pl script
to create the $ORACLE_HOME/nls/data/9idata directory.

After creating the directory, make sure that the ORA_NLS10 environment
variable is set to the full path of the 9idata directory whenever you enable the
10g Oracle home.

Step 7 : Apply additional 10.2.0.4 RDBMS patches

Apply the following patches:

For all UNIX/Linux platforms, apply RDBMS patches:

 6880880 or the latest OPatch version.

 6521934
 6600051
 7496636
 7497678

Do not run any of the post install instructions as those are done as part of the upgrade.

Database Upgrade:

Step 1 : Shut down Applications server processes and database listener .

On each application tier server node, shut down all server processes or services. On the database tier
server node, shut down the Oracle Net or Net8 database listener in the old Oracle home

Step 2 : Prepare to upgrade

Read Chapter 2 of Oracle Database Upgrade Guide 10g Release 2 (10.2) . Take note of the section
pertaining to the Database Upgrade Assistant (DBUA).
Step 3 : Upgrade the database instance

Perform the steps from the "Run the Pre-Upgrade Information Tool" section to the
"Upgrade the Database Using the Database Upgrade Assistant" section of
chapter 3.

We recommend that you use 500 MB as the SYSAUX tablespace size. Set autoextend
on for the SYSAUX tablespace.

If you plan to change the PL/SQL compilation mode, disable the compilation of
objects.

Step 4 : Modify initialization parameters

Use the following sections in document 216205.1

If System Managed Undo (SMU) is disabled in your database instance, ignore the
initialization parameters that begin with "undo_". You will be instructed to configure
them in the next step.

If native compilation of PL/SQL code is disabled in your database instance, ignore

the initialization parameters that pertain to the native compilation of PL/SQL code.

Step 5 : Perform 10.2.0.4 patch set post-installation tasks

Review the "Postinstallation Tasks" section of the patch set notes. Perform the steps
that are relevant for your database.

Step 6 : Install Oracle Data Mining and OLAP

Not Applicable.

Step 7 : Natively compile PL/SQL code (optional)

If you are not on the Windows Itanium platform, you can choose to run Oracle E-
Business Suite 11i PL/SQL database objects in natively compiled mode with Oracle
Database 10g. See the "Compiling PL/SQL Code for Native Execution" section of
Chapter 11 of Oracle Database PL/SQL User's Guide and Reference 10g Release 2
(10.2).

When modifying the initialization parameters pertaining to the PL/SQL native

compilation, use document 216205.1, on My Oracle Support as a guideline. You can
set the plsql_native_library_subdir_count parameter as described in the PL/SQL
user's guide. Create the associated subdirectories for the given
plsql_native_library_dir and plsql_native_library_subdir_count parameters.

I think this one is not require

After the Database Upgrade:

Step 1 :Start the new database listener (conditional) .

If the Oracle Net listener for the database instance in the new Oracle home has not been started, you
must start it now. Since AutoConfig has not yet been implemented, start the listener with the lsnrctl
executable (UNIX/Linux) or Services (Windows). See the Oracle Database Net Services
Administrator's Guide, 10g Release 2 (10.2) for more information.

Step 2 : Run adgrants.sql (conditional)

If you have at least AD.I or E-Business Suite release 11.5.10 installed on your system,
copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql for Windows) from the administration
server node to the database server node. Use SQL*Plus to connect to the database as
SYSDBA and run the script using the following command:
$ sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql)
[APPLSYS schema name]

where [APPLSYS schema name] is the Applications Object Library user, most commonly
named APPLSYS.

Step 3 : Grant create procedure privilege on CTXSYS

Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to

the database server node. If you are upgrading to R12, use the R12 version of the
file. Use SQL*Plus to connect to the database as APPS and run the script using the
following command:
$ sqlplus apps/[APPS password] @adctxprv.sql \
[SYSTEM password] CTXSYS
Step 4 : Implement and run AutoConfig
Implement and run AutoConfig in the new Oracle home on the database server
node. If the database listener of the new Oracle home is defined differently than the
old Oracle home, you must also run AutoConfig on each application tier server node
to update the system with the new listener.

See Using AutoConfig to Manage System Configurations with Oracle Applications

11ion My Oracle Support for instructions on how to implement and run AutoConfig.

Shut down all processes, including the database and the listener, and restart them
to load the new environment settings.

Step 5 : Gather statistics for SYS schema

Copy $APPL_TOP/admin/adstats.sql from the administration server node to the

database server node. If you are upgrading to R12, use the R12 version of the file.
Note that adstats.sql has to be run in restricted mode. Use SQL*Plus to connect to
the database as SYSDBA and use the following commands to restart the database in
restricted mode, run adstats.sql, and restart the database in normal mode:
$ sqlplus "/ as sysdba"
SQL> shutdown normal;
SQL> startup restrict;
SQL> @adstats.sql
SQL> shutdown normal;
SQL> startup;
SQL> exit;

Step 6 : Re-create custom database links (conditional)

If the Oracle Net listener in the 10.2.0 Oracle home is defined differently than the
one used by the old Oracle home, you must re-create any custom self-referential
database links that exist in the Applications database instance. To check for the
existence of database links, use SQL*Plus on the database server node to connect to
the Applications database instance as APPS and run the following query:
$ sqlplus apps/[apps password]
SQL> select db_link from dba_db_links;
The EDW_APPS_TO_WH and APPS_TO_APPS database links, if they exist, should
have been updated with the new port number by AutoConfig in the previous step.

If you have custom self-referential database links in the database instance, use the
following commands to drop and re-create them:

$ sqlplus apps/[apps password]

SQL> drop database link [custom database link];
SQL> create database link [custom database link] connect to
[user] identified by [password] using
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=[hostname])
(PORT=[port number]))(CONNECT_DATA=(SID=[ORACLE_SID])))';
where [custom database link], [user], [password], [hostname], [port number], and
[ORACLE_SID] reflect the new Oracle Net listener for the database instance.

Step 7 : Re-create grants and synonyms

Oracle Database 10g Release 2 (10.2) contains new functionality for grants and
synonyms compared to previous database releases. As a result, you must re-
create the grants and synonyms in the APPS schema. On the administration
server node, as the owner of the Applications file system, run AD Administration
and select the "Recreate grants and synonyms for APPS schema" task
from the Maintain Applications Database Objects menu.

If MRC is implemented in your Applications system, then run the "Maintain

Multiple Reporting Currencies schema" task to re-create MRC triggers in
the Apps schema.

Step 8 : Apply Oracle Receivables patch

Apply Oracle Receivables patch 5753621.

Step 9 : Restart Applications server processes (conditional

Restart all the Application tier server processes that you shut down previously. Remember
that the Oracle Net listener for the database instance, as well as the database instance
itself, need to be started in the 10.2 Oracle home. Users may return to the system

10g release 2 interoperability patch analysis for 11.5.9

 11.5.9 E-Business Suite Consolidated Update 2

 10g Release 2 interoperability patch for 11.5.9 (4653217)

Patch :4653217

Abstract
11.5.9 INTEROP PATCH FOR 10GR2

Update 4653217
Product Applications Updates
Release 11i
Platform Linux x86
Built MAR-30-2006 12:38:41

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

Prerequisite Updates
This patch requires additional prerequisite patches to have been
successfully
applied to your system before it can be applied. These prerequisite
patches, as
at the time that this patch was built, are listed below. Please check
Oracle
Metalink to determine if any of these have been superseded

4489303 - TXK (FND) AUTOCONFIG TEMPLATE ROLLUP PATCH L (NOV 2005)

3599540 - AFLOBBLD.SQL FAILS WITH ORA-00922 MISSING OR INVALID OPTION
3453499 - Patch 11i.ADX.F

Description
This patch should be applied to an 11.5.9.2 environment before upgrading
to 10gR2.

Pre-requisites;

4489303 - TXK (FND) AUTOCONFIG TEMPLATE ROLLUP PATCH L (NOV 2005)

3599540 - AFLOBBLD.SQL FAILS WITH ORA-00922 MISSING OR INVALID OPTION
3453499 - Patch 11i.ADX.F

4489303
So The patch 448930 replacement for this patch 9535311

Abstract
TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH U

Update 9535311
Product Techstack
Release 11i
Platform Linux x86
Built NOV-08-2010 11:55:02

Instructions
Determine if you are using AutoConfig to manage your configuration.
Further information about AutoConfig can be found in Metalink Note
165195.1
"Using AutoConfig to Manage System Configurations with Oracle
Applications 11i".

1. For Non-AutoConfig Customers

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

We strongly urge all EBS 11i customers to use AutoConfig as it is the

only
way to get the technology configurations which are tested by Oracle.
If you
are not using AutoConfig to manage your configuration, then
consult the Oracle MetaLink Note 165195.1 "Using AutoConfig to Manage
System
Configurations with Oracle Applications 11i" Section "5: Migrating
to AutoConfig" to become AutoConfig enabled.

2. For AutoConfig Enabled Customers

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

2.1 Before Applying This Patch

--------------------------

Perform the steps listed below:

2.1.1 Source the Applications environment file as the owner of the

application tier file system.

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

2.1.3 Run the Technology Stack 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=<apps database password>

on Windows [ the command must be entered in one line ]:

%ADPERLPRG% txkprepatchcheck.pl -script=ValidateRollup

-outfile=%APPLTMP%\txkValidateRollup.html
-appspass=<apps database password>

2.1.4 Review the txkValidateRollup.html report generated by the

validation
script. Perform the required actions described in the report
before
you apply this patch.

2.1.5 It is recommended for customers to upgrade to JDK 1.3.1_15 or

higher
on the database tier. Please refer to MetaLink Note 165195.1
"Using AutoConfig to Manage System Configurations with Oracle
Applications 11i" for the JDK upgrade process on the database
tier.

2.1.6 In addition to the above list of patches, customers should be

on
Developer 6i patchset 18 (6.0.8.27) or higher before uptaking
patch
9535311. For detailed upgrade information, please refer to
Oracle
MetaLink Note 125767.1 "Upgrading Developer 6i with Oracle
Applications 11i".

2.2 How To Apply This Patch

-----------------------

This patch contains the following driver file to be applied with

AutoPatch: u9535311.drv (This is the unified driver).

This patch must be applied to all application tier server nodes

(Forms,
Web, Concurrent Processing, Admin) as the Applications file system
owner.

2.3 After Applying this Patch

-------------------------

2.3.1 Run AutoConfig following the instructions in Oracle MetaLink

Note
165195.1 "Using AutoConfig to Manage System Configurations with
Oracle
Applications 11i" on each node where you have applied this
patch. Note
that if you have AD.I, this step might have already been
performed at
patch time by adpatch.

Note: 1. Customers using the AutoConfig Customizations feature

must
merge any customizations with the AutoConfig templates
 provided via this patch before running AutoConfig.
More
detailed information can be found in Oracle MetaLink
Note
270519.1 "Customizing an AutoConfig Environment".

2. Customers using Oracle E-Business Suite with Real

Application
Clusters (RAC) setup on a 10g database are suggested
to set
the value for the context variable s_virtual_hostname
to the
virtual host name before running AutoConfig on the
database
tier. Please refer to MetaLink Note 362135.1
"Configuring
Oracle Applications Release 11i with 10g Release2 Real
Application Clusters and Automatic Storage Management"
for
detailed instructions on configuring the listener with
a
virtual host name on the database tier.

3. Customers running on TXK AutoConfig Rollup Patch Q

(5985992)
or below and still using Discoverer 4i, will need to
update
context variable "s_discostatus" to "enabled" for
disco
service to be enabled. Disco 4i service will be
disabled by
default after applying this patch.

2.3.2 Update the RDBMS ORACLE HOME file system with the AutoConfig
files by
performing the following steps:

2.3.2.1 On the Application Tier (as the APPLMGR user):

2.3.2.1.1 Source the environment file.
2.3.2.1.2 Create the appsutil.zip file by executing:
$ADPERLPRG $AD_TOP/bin/admkappsutil.pl
(On Windows: %ADPERLPRG%
%AD_TOP%\bin\admkappsutil.pl)
This will create appsutil.zip in
$APPL_TOP/admin/out .

2.3.2.2 On the Database Tier (as the ORACLE user):

2.3.2.2.1 Copy or FTP the appsutil.zip file to the
<RDBMS ORACLE_HOME>
2.3.2.2.2 cd <RDBMS ORACLE_HOME>
2.3.2.2.3 unzip -o appsutil.zip
2.3.2.2.4 Run AutoConfig by executing:

<RDBMS_ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/
adautocfg.sh (On Windows use adautocfg.cmd).

2.3.3 If $OA_HTML/bin/appsweb.cfg contains specialized configuration

entries within its "BEGIN CUSTOMIZATION" and "END
CUSTOMIZATION"
section, copy that section to appsweb_<context name>.cfg .
Please confirm even if you have already done this before.
 2.3.4 Customers who have not used the latest version of AutoPatch,
delivered
via AD Minipack 11i.AD.I.4 (4712852), are suggested to
regenerate jar
files by running adadmin, selecting the "Generate Applications
Files"
option, and subsequently selecting the "Generate product JAR
files"
option. The latest version of AutoPatch automatically
regenerates
required jar files, making this step optional.

2.3.5 Remove the log file sec_audit.log from the following

location(s)
if it exists:
* [iAS_ORACLE_HOME]/Apache/Apache/logs/ .
* [iAS_CONFIG_HOME]/Apache/Apache/logs on installations where a
Shared Oracle Home is configured.

2.3.6 If you have "SSL" enabled at the Apache layer then ensure that
a
Certificate Chain (ca.crt) file exists in the following
directory:

%s_web_ssl_directory%/ssl.crt/ca.crt
[where %s_web_ssl_directory% is the Applications context
variable].
It is OK if this file is zero bytes. For more information
on SSL, see Oracle MetaLink Note 123718.1 "A Guide to
Understanding
and Implementing SSL with Oracle Applications 11i".

2.3.7 Stop the application server processes using the script

adstpall.sh.

2.3.8 Restart application server processes using the script

adstrtal.sh.

NOTE: For Oracle Solaris SPARC only.

On this platform, by default, there is a limit on the File

Descriptors
of 255. This can affect the number of Forms sessions that can be
created.
To increase the File Descriptor limit, an Environment Variable is
created
as follows:

LD_PRELOAD_32="/usr/lib/extendedFILE.so.1"

After applying this patch it is possible that warning messages

similar
to the following may be seen:

ld.so.1: mailx: warning: /usr/lib/extendedFILE.so.1: open failed:

illegal insecure pathname
ld.so.1: sendmail: warning: /usr/lib/extendedFILE.so.1: open
failed:
illegal insecure pathname
 These are warning messages and can be ignored. However, to prevent
the
warning messages being generated the library extendedFILE.so.1 needs
to be
made "trusted"

This can be achieved if the directory is listed as trusted in the

file
/var/ld/ld.config.

This file does not exist by default and can be created using the
command:

/usr/bin/crle -c /var/ld/ld.config -l /usr/lib

Please refer to the manual page for crle(1) on your instance for full
information with regard to this command.

Description
TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH U

Patch Contents
==============

1. This patch is applicable for all 11i releases. It includes TXK

AutoConfig
template files to configure the Technology Stack for Oracle E-Business
Suite
11i instances using AutoConfig. These template files have no effect on
the
Oracle E-Business Suite configuration until the AutoConfig utility is
run.

2. This patch also contains the latest AutoConfig Engine and Tools
related
enhancements and fixes.

3. All TXK Rollup Patches are cumulative. This patch contains additional
content
on top of TXK AUTOCONFIG ROLLUP PATCH T(8217898).

4. This RUP patch now delivers Advanced Configuration Wizards, including

and
superseding 5011249 - TECHSTACK ADVANCED UTILITIES ROLLUP C (APRIL
2006)

5. This RUP has dependencies on EBS patches as well as technology stack

patches. The EBS patch requirements are listed in the Prerequisite
Listing
section below. The technology stack requirements are listed in the
txkValidateRollup report.

Features & Enhancements

=======================
1. Applications password validation while using adcmctl and in other
various
commands.
2. Mini AutoConfig: it is possible now to run AutoConfig using a
customized driver.
3. AutoConfig performance improvements.
4. adchkcfg enhancements to remove false diffs/false positives
5. DB 11gR2 support.
6. OHS related chages for security and refining of aliases, log names
changed as
per standards
7. Addition of ANTISAMY run-time rehosted JAR files.
8. OHS performance improvements by removing loading of unwanted modules.
9. For DB tier on Solaris 64-bit platform, use of 64-bit JVM during CVM
phase
of AutoConfig.
10. Support for DB listener name customization.
11. Support of Forms and Reports in the Icelandic language.
12. Addition of LOCAL_LISTENER parameter to init.ora template.
13. Introduction of FORMS60_RECORD_GROUP_MAX to restrict the number of
records
fetched by an LOV.
14. New context variables: s_httpd_pls_pid_file, s_icx_language,
s_forms60_record_group_max. s_db_listener.

IMPORTANT Note
========= ====
A new context variable s_db_listener is introduced in RUP-U to enable
customer-defined listener names.

In an existing instance having default listener names, applying RUP-U

would
update the context variable s_db_listener to default values.

AutoConfig supported default DB listeners (pre Techstack RUP U) are:

RAC - LISTENER_<HOSTNAME>
nonRAC - <SID>

Prior to RUP-U there was no AutoConfig support for non-default listener

name. If
an existing instance has non-default listener name, applying RUP-U will
result
in incorrect instantiation of listener.ora. So you are advised to ensure
that
listener name has default values before applying RUP-U.

If due to any reason, your listener name is incorrect, you can run
AutoConfig
again by updating the value of context variable s_db_listener to desired
non-default listener name to get intended listener name.

Related Notes
=============

Additional information related to this patch can be obtained in the

following
Oracle MetaLink Notes:

165195.1 "Using AutoConfig to Manage System Configurations with

Oracle Applications 11i".
218089.1 "Frequently Asked Questions About Using
AutoConfig With Oracle Applications Release 11i".
217368.1 "Advanced Configurations and Topologies for Enterprise
Deployments
of E-Business Suite 11i".
362135.1 "Configuring Oracle Applications Release 11i with 10g Release2
Real
Application Clusters and Automatic Storage Management"
123718.1 "A Guide to Understanding
and Implementing SSL with Oracle Applications 11i".
125767.1 "Upgrading Developer 6i with Oracle Applications 11i".

It is It is recommended for customers to upgrade to JDK 1.3.1_15 or higher

on the database tier. Please refer to MetaLink Note 165195.1

But we will upgrade this in later

2.1.6 In addition to the above list of patches, customers should be on

Developer 6i patchset 18 (6.0.8.27) or higher before uptaking patch
9535311. For detailed upgrade information, please refer to Oracle
MetaLink Note 125767.1 "Upgrading Developer 6i with Oracle
Applications 11i".

We must have to upgrade Devloper 6i patchset 18

Current version is :6.0.8.21 so we need to upgrade before applying the patch 9535311

Upgrading Developer 6i with Oracle Applications 11i (Doc ID 125767.1)

How to Check the Developer 6i Version

he Developer 6i patchset level can be checked either by launching a form within

Oracle E-Business Suite or from the Server. Developer 6i patch versions correlate to
the Forms version as follows:

6.0.8.28.x = Developer 6i Patch 19

Check the Version from a Form in Oracle E-Business Suite

Log in to Oracle E-Business Suite and access any Form

Select 'Help -> About Oracle Applications' from the menu bar and check the 'Oracle
Forms Version' displayed in the 'Forms Server' section. For example:
----------------------------------------
Forms Server
----------------------------------------
Oracle Forms Version : 6.0.8.28.0

(If no data shows under the 'Forms Server' section please check the profile option
'FND: Diagnostics' is set to 'Yes' and re-check)

Step 2: Download the latest Certified Developer 6i Patchset and Applications

Interoperability Patch

Step 3: Download Additional Developer 6i Patches

You will need to separately obtain certain additional Developer (Forms) patches,
depending on your Developer Patch and Platform.

These patches must be applied BEFORE any Forms security CPU patch. The
CPU patch is designed to be applied on top of these patches. Any conflicts between
the patches listed here and the CPU should already be resolved in the CPU patch by
Oracle Development. If any of these patches are already merged into the CPU patch,
it is not strictly necessary to apply the non-CPU patch first, but it will not cause a
problem if you have already done so. Applying these patches AFTER the CPU may
cause problems if the two patches update common files, and is therefore not
supported. If you discover unresolved conflicts between the patches listed here and
the CPU, please log a tar with Oracle Support.

There is no automatic conflict checking in Developer 6i, so if you apply additional

one-offs, other than the ones listed here or the CPU, you should check for conflicts
in the files updated, and request merged fixes through Oracle Support as necessary.

Forms and Reports is a 32 bit application. The patches that are available for 64 bit
OS will also be applicable for 32 bit OS unless specified otherwise.
For Developer 6i Patch 19 on Sun Solaris, IBM AIX, Linux, HP Tru64 and Microsoft
Windows Servers. Where applicable please ensure you download the 6.0.8.28
version of the patch:

Developer 6i Sun Solaris HP-UX IBM AIX Linux HP Tru64 MS Wind

1
Patch 19 Patch 22709024 3 Patch 7423534 Patch 22709024 3 Patch 22709024 3 Patch 16699473 Patch 19
3
Patch 22709024

The above additional patches is not compulsory, “These

patches must be applied
BEFORE any Forms security CPU patch”Hence I am not going to apply
this patch

Step 4: Stop the Forms, Reports, HTTP, and Concurrent Manager Servers

You must stop all server processes that may be impacted by the Developer 6i patch
before applying it.

Stop the Forms and Reports server processes.

For Microsoft Windows platforms, note the name of the Forms and Reports services
in Control Panel - Services.Also for Microsoft Windows platforms, stop all Forms user
connections still active. To do this, open Task Manager and kill all processes
named ifweb60.exe or ifsrv60.exe .

Stop the HTTP server used for your Forms server.

Stop the Concurrent Manager servers as they will need to use the new Reports
executable.

For Microsoft Windows platforms also shut down the 'OracleTNSListener80APPS_SID'

& 'Oracle TCF SocketServer SID' Services.

Step 5: Install the Developer 6i Patch(Patch:6194219)

NOTE: All references to ORACLE_HOME refer to the 8.0.6 based Oracle Home.

Step 7: Relink Applications Executables on UNIX Platforms

After applying the Oracle Developer 6i Patch on UNIX platforms, you must relink several
Oracle E-Business Suite executables to include Developer patch changes. The executables
are f60webmx, ar60run , ar60runb, ar60rund, and are all owned by FND.
NOTE: If your environment is NOT Autoconfig enabled, make sure you have modified the
LD_LIBRARY_PATH or SHLIB_PATH variable as indicated in step 6 above, before performing
this step, or the relink will fail.

You can relink these executables by running adadmin

When the Main Menu appears select 'Maintain Applications Files Menu' and then
select 'Relink Applications Program'
Answer the questions below as follows, in order to select the individual executables
for relinking.

Enter list of products to link

('all' for all products)[all] : fnd
Generate specific executables for each selected product [No] ? y
Relink with debug information [No] ? n

(You will then be offered a list of executables that are available for relinking)

Enter executables to relink, or enter 'all' [all] : f60webmx ar60run ar60runb

ar60rund *

* In a multi-node configuration, not all these executables exist on each node. The
list of executables will show those that do exist on the node you are currently
running on, and only those should be entered to avoid errors.

Step 8: Apply the Oracle Applications 11i Interoperability Patch

Apply the Applications/Forms Interoperability Patch you downloaded. If this

document was referenced from another patch, apply that patch, as well.

Step 9: Configure Applications to use Sun JRE Native Plug-in

Step 10: Verify your 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 and the previous steps completed successfully, run the AD Administration Utility
(adadmin), select Maintain Applications Files, then select Generate Product JAR Files.
Do not force the regeneration of all JAR files. Again, verify that
the fndforms.jar and fndewt.jar JAR files have been rebuilt by checking their timestamps
again.

If your JAR files are still not updated, verify all the prior steps, and the Known
Issues section below.

If you 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' on Unix
platforms and '%ORACLE_HOME%\bin\ifcmp60.EXE help=y' on Windows to display
various component versions. (If the version shown is still 8.0.6.0.x please refer to
My Oracle Support Knowledge Document 191573.1)

For Microsoft Windows platforms, look under Control Panel - Services to see if
additional Forms and Reports services were added. If so, disable the new ones by
pressing the Startup button, and setting the Startup Type to Disabled.

Step 11: Start the Forms, Reports, HTTP, Concurrent Manager Servers

Restart the listener processes, as follows:

 Restart the Forms and Reports server processes. On Microsoft Windows Server, start
the original Oracle Forms Server service you stopped earlier, if it is not already
running.
 Restart the HTTP server used by the Forms server if it is not already running.
 Restart the Concurrent Processing server (the concurrent managers).
 On Microsoft Windows platforms also start the 'OracleTNSListener80APPS_SID' &
'Oracle TCFSocketServer SID' Services.

So I am applying this patch 9535311

3599540
Update
Product Application Object Library
Release 11i
Platform Linux x86
Built JUL-19-2004 14:43:45

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

This patch should be applied to ALL tiers.

Description
This patch includes some basic enhancements and code clean up for the
FND_LOBS
index creation. It should ONLY effect the Web iHelp search engine -
iHelp must
already be properly configured to access the search engine and this patch
should
have NO effect on iHelp files or configuration.