Beruflich Dokumente
Kultur Dokumente
2)
Doc ID: 415222.1 Type: ANNOUNCEMENT
Modified Date : 15-DEC-2008 Status: PUBLISHED
In this Document
What is being announced?
Steps to Maintain Oracle Application Server 10g Release 2 (10.1.2)
What do you need to do?
Check Oracle Application Server 10g Installation Type
Understanding Supplied Oracle Database Component Version
Step 1: Ensure Certified Oracle Database Component is Updated
*** Preferred Update is Oracle Application Server 10.1.2.2 in Step 3 ***
10.1.0.4.0 Patchset for AS 10.1.2.0.0 or 10.1.2.0.1
10.1.0.5.0 Patchset (Patch 4505133) for AS 10.1.2.0.2 or 10.1.2.1
Step 2: Test Success of Oracle Database Patchset
Step 3: Apply Latest Oracle Application Server 10.1.2.2 Patchset (Patch 4960210)
Step 4: Apply Required Patches After 10.1.2.2 Patchset
Step 5: Install Latest OPatch (Patch 6880880) to all Oracle Application Server homes
Step 6: Apply Forms Patch 5488476 on UNIX if Oracle Forms Installed
Applies to:
If following the below steps, you will prepare Oracle Application Server 10g for any subsequent patching,
including Critical Patch Updates and new Daylight Saving Time requirements.
Important:
This document only applies to Oracle homes installed from the Oracle Application Server 10g
Release 2 (10.1.2) media, outlining the patching recommendations to maintain Oracle Application Server
10g Release 2 (10.1.2).
If any other media was used to install Application Server components, its important to ensure the steps are
certified with the product being used. (e.g. DB 10.2 Companion CD homes, Grid Control 10.2.0.3 homes,
and E-Business Suite usage; where specific patching steps applicable to those products are required. It
may be similar, yet there can be minor, but important, differences).
Notes:
• If Oracle Identity Management (IM) 10.1.4.0.1/10.1.4.2 or Oracle Portal 10.1.4 has been applied
to this Oracle Application Server 10g Release 2 (10.1.2) home, the installation will still have its AS
10.1.2.x version to maintain. See "IM 10.1.4.0.1" or "Portal 10.1.4" references within this Note for
more information pertaining to each step.
• If there is an external Oracle Database (e.g., 9.2 or 10.2) used for the Metadata Repository, it is a
separate home to be maintained separately, (except for Metadata Repository Updates, as part of
an Oracle Application Server Patchset step).
• Oracle Application Server 10g Release 2 (10.1.2) Companion CD installs Oracle HTTP Server
Standalone as two options, based on Apache 1.3 or Apache 2.0. Application Server 10.1.2.x
Patchsets may be applied to these homes to update the standalone products and associated
components.
• Since the Oracle Database Server 10g Release 2 (10.2) provides a Companion CD installing an
Oracle HTTP Server version 10.1.2.0.0, similar guidelines for this home can be found in the
following document:
Note 400010.1 Steps to Maintain Oracle Database 10.2 Companion CD Home (for Oracle HTTP
Server)
The purpose of this document is to reiterate maintenance information from Note 329361.1, (Tables
1-3), in a step-by-step format after explaining product version concepts.
Note 329361.1 Oracle Application Server 10g Release 2 (10.1.2) Support Status and Alerts
The first thing any administrator should do is obtain the exact Version and InstallType of an Oracle
Application Server 10g Release 2 (10.1.2) installation. To determine this information from an already
installed Oracle home, check the installed product information using the Oracle Universal Installer (OUI),
or view the [InstallData] section in the contents of the ias.properties file, where Version and InstallType are
listed.
The ias.properties file is located in the following directory:
UNIX:
$ORACLE_HOME/config/ias.properties
Windows:
%ORACLE_HOME%\config\ias.properties
Follow the below steps for a given installation after obtaining the exact Version and InstallType from Oracle
Universal Installer (OUI) or ias.properties. Then, decide which Oracle home will be administered. For
purposes of patching, Oracle Application Server homes are commonly referred to as "middle tier" or
"infrastructure" home types, using the guideline below:
[Bullets below show InstallType from ias.properties, followed by full name]
In all Oracle Application Server 10g release 2 (10.1.2) installations, there is an installed Oracle Database
component. On infrastructure homes, this may be a full Database Instance. On middle-tier homes, this is
the client networking components. This is an important concept throughout the Oracle Application Server
patching, as many patches are based on this version or require a minimum version of the Oracle Database
component. The following lists the database server/client component version installed from Oracle
Application Server 10.1.2 media:
Windows:
%ORACLE_HOME%\OPatch\opatch lsinventory
Important: If taking the recommendation to apply the latest Oracle Application Server 10gPatchset, Patch
4505133 (10.1.0.5.0 Patchset) needs to be applied only to an Oracle Database Server instance installed in
the Oracle home. (If using a 9.2 or 10.2 Oracle Database Server for the Metadata Repository, no
Database Patchset is required).
The Oracle Database Component is automatically updated to 10.1.0.5 in non-database homes when
applying the latest Oracle Application Server 10g Patchset. (e.g. Standalones or Mid-Tiers). This allows
you to skip the remainder of this section, which is only supplied for reference, if planning a later update,
staying on a pre-AS-Patchset version.]
To update the installed Oracle Database Component, a Oracle Database Server Patchset must be
downloaded and installed by Oracle Universal Installer (OUI). Only Oracle Database 10.1.0.4.0 and
10.1.0.5.0 Patchsets are certified to be installed into homes installed with Oracle Application Server 10g
Release 2 (10.1.2) media, depending on the actual 10.1.2.x.x version.
Notes:
• When 10.1.0.4.0 or 10.1.0.5.0 is a requirement of another patch, the Database Patchset must be
installed in all Oracle Application Server homes.
• Since 10.1.0.4.0 is only intended for AS 10.1.2.0.0 or 10.1.2.0.1 homes, where Error Correction
has now ended, its recommended to apply the latest Application Server Patch Set to remain
supported.
For Oracle Application Server 10g Release 2 (10.1.2) homes containing an Oracle Database Server, the
Patchset Release Notes should be followed. For non-database homes, (e.g., Standalone or Mid-Tiers),
only use of OUI is required, nothing to follow in the Patchset Release Notes.
10.1.0.4.0 Patchset for AS 10.1.2.0.0 or 10.1.2.0.1
Patch 4163362 (10.1.0.4.0 Patchset) should be applied to all Oracle Application Server 10.1.2.0.0 and
10.1.2.0.1 homes. See Note 329361.1, Table 1, for more 10.1.0.4.0 information. It is now recommended
that Oracle Application Server 10.1.2.0.0 and 10.1.2.0.1 homes be updated with Oracle Application Server
10.1.2.2 Patchset.
Note: If you are not planning to apply any Oracle Application Server patchset, the 10.1.0.4.0 Patchset
(Patch 4163362) is a minimum requirement to many other patches, including past Critical Patch Updates
and Daylight Savings Time updates. Error Correction Support has ended on this version to comply with
Oracle Error Correction policy in Note 209768.1. Therefore, it is recommended to apply the latest
Application Server Patch Set to remain supported.
Patch 4505133 (10.1.0.5.0 Patchset) should be applied to all Oracle Application Server 10.1.2.0.2 homes.
If Oracle Application Server 10.1.2.1 Patchset has already been applied, it should be ensured that Patch
4505133 (10.1.0.5.0) is also applied to all Oracle Application Server 10.1.2.1 homes. See Note 329361.1,
Table 1, for more 10.1.0.5.0 information. It is now strongly recommended that these homes be updated
with Oracle Application Server 10.1.2.2 Patchset, where the 10.1.0.5.0 update is automatically applied to
non-database homes.
Notes:
• If you are not planning to apply any Oracle Application Server patchset, the
10.1.0.5.0 Patchset (Patch 4505133) is a mimimum requirement to many other
patches, including Critical Patch Updates and Daylight Savings Time.
If not applying the required Oracle Database Patchset to update its component in the Oracle Application
Server home, subsequent patching may not be successful, resulting in an error described in the following
document:
Note 338338.1 Opatch Fails with Missing_component - Oracle.Rsf.Rdbms_rsf, 10.1.0.4.0 (or 10.1.0.5.0)
• Linux 64
If using Windows with a 64-bit processor, the Oracle Database 10.1.0.5 Patchset (Patch 4505133) should
be downloaded as "Windows-32bit", as the Database installed is 32-bit.
Note: If applying the latest AS Patchset, Refer to its Release Notes or Step 4 within this document specific
to AS 10.1.2.2. However, since it is necessary to apply 10.1.0.5 to an Infrastructure Database (10.1)
instance before applying any AS Patch Set, see Note 359362.1 for applicable (Infrastructure only) issues
which could arise on your system.
If applying Oracle Database Patchset 10.1.0.4.0 or 10.1.0.5.0 using above guidelines, always test your
installation before continuing. This is to ensure all issues are resolved before moving to the next step.
For Oracle Application Server 10g version 10.1.2.0.2, there are a few known issues after applying the
10.1.0.5 Patchset, most of which are documented in Note 329361.1, Table 1:
Note 359362.1 Known Issues With DB 10.1.0.5 Patchset to AS 10.1.2 homes
Step 3: Apply Latest Oracle Application Server 10.1.2.2 Patchset (Patch 4960210)
Important:
Oracle Application Server 10g Patch Set 3 (10.1.2.3) is now available. It is recommended
to apply 10.1.2.3 following Note 329361.1, Table 2. Then come back here and follow
Section 5.
If applying 10.1.2.3, skip Step 3 and 4 below, and continue with Step 5 of this
document. The 10.1.2.2 information remains here for reference purposes or if needing to
apply 10.1.2.2 for another reason. (e.g., certifications with another product)
• It is now strongly recommended that all Oracle Application Server 10g Release 2 (10.1.2.x.x)
homes be updated with the 10.1.2.2 Patchset, (Patch 4960210). Before applying, Patch 4505133
(10.1.0.5.0 Patchset) needs to be applied to the Metadata Repository Database Instance (If its
Oracle Database 10.1.x). Non-database homes are automatically updated with the Oracle
Database Component version 10.1.0.5.0.
• If Oracle Portal 10.1.4 has been applied to an Oracle Application Server 10g (10.1.2.0.2) home,
the AS 10.1.2.2 Patchset will update Oracle Portal to version 10.1.4.1. Upgrading to Portal 10.1.4
is currently optional, but once on Portal 10.1.4, it is mandatory to upgrade to Portal 10.1.4.1. If
Portal is upgraded to version 10.1.4 after the AS 10.1.2.2 Patchset, the AS 10.1.2.2 Patchset may
be run a second time to detect the required 10.1.4.0 to 10.1.4.1 upgrade.
• If on Linux-x86 and Oracle BPEL 10.1.2.0.2 is installed, it is important to first apply Patch
5879130, order to avoid the following problem:
Note 428008.1 Installing 10.1.2.2.0 Patchset with BPEL: "Global Variable does not exist:
oracle.tip.s_DBPasswd"
After updating Oracle Application Server 10g with the 10.1.2.2 Patchset on Sun Sparc Solaris and
Microsoft Windows, apply Patch 5732133 to complete the 10.1.2.2 update. Its only after this, will you have
truly updated to version 10.1.2.2. On Windows, you must also then apply Patch 6062255 . More
information regarding this is available in the following document:
Note 404477.1 Mandatory Patch for Application Server 10g R2 10.1.2.2 on Solaris and Windows
Important: See "Important Update April 6, 2007" for Windows within Note:404477.1.
After updating Oracle Application Server 10g with the 10.1.2.2 Patchset on Linux, HP, and AIX Platforms,
Patch 5861907 must be applied before applying any other patch with OPatch. The symptoms and
explanation for this issue is in the following document:
Note 413788.1 Applying a One-Off Patch On All Operating Systems Except Windows and SPARC Solaris
After Application Server Patchset 2 (10.1.2.2)
HPUX Itanium
Patch 7019450 has been provided to resolve an issue with OC4J containers from starting, which only
renderes itself after further patching. It is required to apply this patch before applying a Critical Patch
Update.
AIX Only:
Note 747493.1 SQL*Plus Banner Still Shows Version 10.1.0.4.2 After Application Server Patch Set
After updating Oracle Application Server 10g with the 10.1.2.2 Patchset on the AIX Platform, Patch
5983475 is required if using or planning to use Oracle Web Cache on a port below 1024. This patch
provides a new env_calypso.mk to be compatible with the required root permissions.
@Bug 5983475, Bug 5901143
Jinitiator Update
After updating Oracle Application Server 10g with the 10.1.2.2 Patch Set on an Oracle home with Oracle
Forms installed, the Jinitiator version is updated to version 1.3.1.26. If the Jinitiator version was already
upgraded to a newer version beforehand, then it would downgrade the Jinitiator version to 1.3.1.26.
JInitiator 1.3.1.28 (Patch 5882294 or later) should be applied after the 10.1.2.2 Patch Set.
When Oracle Forms is installed on an Oracle Application Server 10g middle tier, it is necessary to apply
Patch 5841985 to update with a new genshlib. This should be installed even if Oracle Forms is not used to
resolve a relinking issue that will occur with future patching.
The Readme for the 10.1.2.2 Patch Set has a section titled, "8.7 Installing Patch 4700543 for OracleAS
Web Cache". This has some updates and clarification since that writing.
If you are using Oracle Web Cache with SSL configured, users may experience issues accessing your site
using an IE browser. If this is the case, you should download and apply a patch to fix an issue with the NZ
layer, bug #4700543. The fix of Oracle Web Cache bug #4503759, (which is included in AS 10.1.2.2 Patch
Set), requires the fix of network bug #4700543. If this fix is not installed, then Internet Explorer 6.0 will not
be able to access Oracle Web Cache with SSL.
Since release of Patch 4700543 (UNIX) has been delayed, if this patch is not available for your platform,
(UNIX) and you experience this problem, please ask Oracle Support to file a Backport Request for you.
The following is what you should apply, depending on the platform, and other patching considerations:
• On UNIX, apply Patch 4700543 after installing OracleAS 10g Release 2 Patch Set 2 (10.1.2.2).
• On Windows, apply Patch 5057606 (10.1.0.5.2). Note that if applying Critical Patch Updates, you
will also obtain this fix, and not require Patch 5057606. If applying both, they will conflict, and you
should choose the latest CPU patch, as that will be the latest cumulative 10.1.0.5.x.
• Note that the fix is generally intended for homes with Oracle Web Cache installed (middle-tiers),
in order to fix the NZ (networking) communication with Oracle Web Cache. The patch is labeled
for "10.1.0.5" because this is an issue with the NZ layer, part of the Oracle Database networking
component. Therefore, this patch can be applied to all homes.
If before applying the 10.1.2.2 Patchset, you had previously made changes to the JDK to be compliant with
2007 Daylight Savings Time changes, (Note 417277.1), you should verify the JDK version in use or re-run
the tzupdater tool to ensure the updates are in tact. Depending on the operating system, the JDK may
have been updated with the Patchset.
While this Note is not specifically for patching Grid Control homes, an important issue is the fact that after
applying, the Inventory skewed because the 10.1 OUI has updated primarily for 10.1-based homes. The
following Note describes this issue, and the solution:
Note 566418.1 How to Recover OUI to 10.2.0.3/10.2.0.4 after Applying IAS 10.1.2.2 Patchset on Grid
Control OMS Home
Step 5: Install Latest OPatch (Patch 6880880) to all Oracle Application Server homes
OPatch is a required patching utility for all one-off patches, which are not part of a Patch Set. This includes
the Critical Patch Updates. For Oracle Application Server 10g, only OPatch 10.1 should be used. (Do not
use OPatch 10.2 for Oracle Application Server versions). Use Patch 6880880 to obtain the latest OPatch
utility before applying any patch that is applied using OPatch. It should be simply extracted into the Oracle
home over the original directory.
On Solaris 10, OPatch may report validation errors, requiring Sun Patch 123908-01 to resolve. Please see
the following OracleMetaLink Document for more information:
Note 4967132.8 Bug 4967132 - Sol: Using "opatch" on Solaris 10 Reports Validation Errors
If Oracle Forms is installed in any Oracle Application Server 10g Release 2 (10.1.2.0.2), apply Patch
5488476. This should be installed even if Oracle Forms is not used. While there are some Forms
functionality fixes, the main requirement is to resolve a relinking issue that will occur with future patching.
This is as per the following document where Patch 5042134 was superseded by Patch 5488476:
Note 361993.1 Makefile Fails to Apply Any One-Off Patch on AS 10g Version 10.1.2.0.2
Linux 64
On Linux x86-64 (AMD64/EM64T), please apply Patch 5852265 instead of Patch 5488476, as changes
were required to be compatible with this OS.
If following the above steps, you will be on certified version of the Oracle Database Component, aligning
Oracle Application Server for a certified level for any subsequent patching, including Critical Patch Update
and Daylight Saving Time requirements.
Oracle currently delivers the latest Critical Patch Updates on a quarterly basis: January, April, July, and
October of each year. You should continually install these updates to secure your installation. In the
following link, look for the latest Oracle Security Advisory, and links to obtain the latest patches:
Critical Patch Updates (CPU) and Security Alerts
Notes:
• Always obtain patches released for your final Oracle Application Server 10g
Release 2 10.1.2.x.x version and your final Oracle Database Component 10.1.x.x
installed in the Oracle home. Patches may be released individually or combined,
depending on the issue and component to be updated.
References