Oracle Applications

Release 11.5.10.2 Maintenance Pack

Installation Instructions
November 2007
Attention
This set of installation instructions, and the documents it references, are the
only instructions required for the installation of the Release 11.5.10.2
Maintenance Pack. It is not necessary to refer to the README-type files
included in the top level of the maintenance pack patch directory. Their
existence in that location results from being individually included in one or
more patches, minipacks, or family packs bundled within the maintenance
pack.

Section 1: Pre-Update Tasks

The tasks in this section are required. They can be performed at any time prior to the application
of this maintenance pack. Complete them in the order listed.
Updated versions of the patches and documents may be available. Go to OracleMetaLink or
contact Oracle Support Services for the latest versions.
Attention
The MRC schema is no longer required for Multiple Reporting Currency
functionality. It is not necessary to synchronize the MRC schema either before
or after you apply the maintenance pack, and you can remove the MRC
schema after you complete the maintenance pack application.
1. Determine Required Steps (optional)
The Upgrade Manual Script for the Maintenance Pack (TUMS-MP) examines your
current configuration and creates a report detailing which of the steps in these
instructions you must complete and which steps you can ignore. Because TUMS-MP
reports on a unique configuration, its output is relevant only to your update. Following
the guidelines in the TUMS-MP report can reduce the time is takes to perform the update.
Run TUMS-MP by applying patch 4238286 and following the instructions in the
associated readme file. Apply the patch on the administration server node.

2. Apply the AD Minipack

Apply AD Minipack I.2 (4337683) on all application tier server nodes. You must have
implemented AutoConfig to apply this patch. If you have not, you can do so as part of the
AD minipack application.
Note
AutoConfig simplifies the management of the various system component
configuration files. Once it has been implemented, you must use it for all
configuration management rather than editing configuration files directly.
3. See the following documentation resources for more information: About Oracle
Applications DBA MiniPack 11i.AD.I.2 (Doc ID: 233044.1, Using AutoConfig to Manage
System Configurations with Oracle Applications 11i (Doc ID: 165195.1), and Frequently
Asked Questions About Using AutoConfig With Oracle Applications Release 11i (Doc ID:
218089.1).
4. Update AutoConfig technology stack templates
The AutoConfig engine relies on template files that are merged with your
implementation-specific data to create necessary configuration files. Update to the latest
technology stack template files by applying patch 4104924.
5. Install Planner libraries (conditional)
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. You
apply this patch manually rather than with AutoPatch. Follow the instructions in the
readme file carefully.
You can determine the installation status of all products by reviewing the Oracle
Applications Database Configuration report. Run $AD_TOP/sql/adutconf.sql
(UNIX/Linux) or %AD_TOP%\sql\adutconf.sql (Windows) on the administration server
node to create the report.
Here is a list of the products that require ILOG Planner libraries.
Short Name

Product Name

eng

Engineering

mso

Constraint Based Optimization

msr

Inventory Optimization (originally Risk Optimization)

mst

Transportation Planning

wip

Work in Process

wps

Manufacturing Scheduling

1. Prepare Payables for update (conditional, optional)

You can reduce the amount of downtime required to apply the maintenance pack by
submitting the Payables Accounting Process for each of your organizations beforehand.
In order to submit this process, all of the following conditions must be true:
o

Payables is registered

You are upgrading from Release 11.5.7 or earlier

You have not already applied Payables Minipack 11i.AP.J (first included in
Release 11.5.8)

You account for Payables transactions using the Payables Accounting Process (as
opposed to using the Global Accounting Engine)

To submit the report, follow these steps:

From the Payables Manager responsibility, navigate to the Requests form (Other>Requests->Run).
Select "Payables Accounting Process" in the Name field.

Use the Tab key to open the Parameters window (if it doesn't open automatically).

Enter the following parameter values. Accept default values for all other
parameters.

Account From Date: [Leave this blank]

Account To Date: [Leave this blank]
Document Class: [All]

Submit the process.

Be sure to repeat this procedure for each organization.

Prepare Service for update (conditional)
Parts of the Service product were migrated to the Install Base product beginning with Release
11.5.6. Service requires new profile options that affect the installation of the maintenance pack.
If any Service products are registered, and you are not already using Release 11.5.6.

1. Deinstall application tier services (Windows only)

This maintenance pack changes the way certain application tier services are defined and
started on Windows platforms. Once all application tier services are shut down, deinstall

the following services (if they exist) from each application tier server node running
Windows.
To remove...

Run command...

Apache Server

%COMMON_TOP%\admin\install\<CONTEXT_NAME>\adsvapc.cmd
-deinstall

Forms Server

%COMMON_TOP%\admin\install\<CONTEXT_NAME>\adsvfrm.cmd
-deinstall

TCF Socket
Server

%COMMON_TOP%\admin\install\<CONTEXT_NAME>\adsvtcf.cmd
-deinstall

Fulfillment
Server

%COMMON_TOP%\util\OamkSvc.exe -sr "Oracle Fulfillment Server

<CONTEXT_NAME>"

iProcurement
Server

%COMMON_TOP%\admin\install\<CONTEXT_NAME>\icxblksvc.cmd
-deinstall

ICSM

%IEO_TOP%\admin\scripts\<CONTEXT_NAME>\ieontics.cmd unregister

2. Confirm that the services are removed by searching for them in the Windows Services
applet.