Steps to Maintain Oracle Application Server 10g Release 2 (10.1.2) (Doc ID 415222.1)

Last updated on JUNE 20, 2021

Applies to:

Oracle Fusion Middleware - Version 10.1.2.0.0 to 10.1.2.3.0 [Release AS10gR2]
Information in this document applies to any platform.
Oracle Application Server 10g Enterprise Edition

Details

Steps to Maintain Oracle Application Server 10g Release 2 (10.1.2)

If following the below steps, you will prepare Oracle Application Server 10g for any subsequent patching, including Critical Patch Updates or 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 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

Actions

Check Oracle Application Server 10g Installation Type

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 version and installation type by viewing 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
An example entry to refer to:

[InstallData]
Version=10.1.2.0.2
InstallType=Business
--example--

A full installation of Oracle Application Server consists of the Oracle Application Server middle tier and the Oracle Application Server infrastructure, installed in separate Oracle homes. However, this can be a distributed (non-collocated) infrastructure, where there are separate Identity Management and Metadata Repository homes. It's also possible that the Metadata Repository home is installed from Oracle Database Server media, (e.g., 9.2 or 10.2). The simplest installation would be one Oracle home on one host system. It is recommended that all administration be performed one Oracle home at a time to avoid confusion across multiple homes.

Follow the below steps for a given installation after obtaining the exact Version and InstallType from the 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]

The middle tier is installed using the following installation options

core = J2EE and Webcache
Portals = Portal and Wireless
Business = Business Intelligence and Forms

The following standalone installations are considered middle tier:

N/A (no ias.properties file) = Oracle Web Cache Standalone
N/A (no ias.properties file) = Oracle HTTP Server Standalone
FRServices = Oracle Forms and Reports Services Standalone
BIServices = Oracle Business Intelligence Standalone

The infrastructure is installed using the following possible installation options:

Infrastructure = Metadata Repository and Identity Management (default infrastructure)
Infrastructure_Meta = Metadata Repository only
Infrastructure_ID = Identity Management (OID and SSO)
Infrastructure_ID = Identity Management (OID only)
Infrastructure_ID = Identity Management (SSO only)

Note:
You may also check the installed product information using the Oracle Universal Installer (OUI). For more details see the following:

<Note 416489.1> How to Find Out the Full Current Version of OracleAS 10g Instance Residing on a Machine

Understanding Supplied Oracle Database Component Version

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 life cycle, 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:

10.1.2.0.0 installation media installs 10.1.0.3.1 in all home types

10.1.2.0.1 installation media installs 10.1.0.3.1 in all home types

10.1.2.0.2 installation media installs 10.1.0.4.2 in all home types

10.1.2.1 patchset media installs 10.1.0.4.2 in non-database homes

10.1.2.2 patchset media installs 10.1.0.5.0 in non-database homes

10.1.2.3 patchset media installs 10.1.0.5.0 in non-database homes

Using OPatch, you may get a listing of all installed components:

UNIX:
$ORACLE_HOME/OPatch/opatch lsinventory

Windows:
%ORACLE_HOME%\OPatch\opatch lsinventory

Step 1: Apply Oracle Database Server 10.1.0.5.0 Patch Set

If taking the recommendation to apply the latest Oracle Application Server 10g Patchset 3 (10.1.2.3), then the Oracle Database Server 10.1.0.5 Patchset (<Patch:4505133>) needs to be applied to any associated Oracle Database Server 10.1 instance. If using a 9.2 or 10.2 Oracle Database Server for the Metadata Repository, no Database Patchset is required.

The Oracle Database client side components are 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). If you are not going to be applying the Oracle Application Server 10g Patchset 3 (10.1.2.3), then you may also apply Oracle Database Server 10.1.0.5 Patchset (<Patch:4505133>) to any 10.1.2.0.2 or 10.1.2.1 home. (e.g., if required to apply a one-off patch delivered only for the 10.1.0.5 component).

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, unless 10.1.2.2 or 10.1.2.3 is applied.

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.

If not applying the required Oracle Database and/or Application Server 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)

Important Platform Specific Steps:

New Certifications (RHEL5, OEL5, SLES10, HP10.31)

On platforms where there has been a newer certification with Oracle Application Server 10g Release 2 (10.1.2), the 10.1.0.5 installer may fail on pre-requisite checks. To workaround this, use "./runInstaller -ignoreSysPreReqs" when starting the installer.

All Linux:

<Note.1232573.1> Requirement to Apply 10.1.0.5 Patch Set to 10.1.2.3 Middle-Tier Homes on Linux

Linux x86-64

If using a Linux 64-bit OS, choose a Database Patchset on My Oracle Support labeled for Platform "Linux x86" and use 32-bit shell emulation with the "linux32 bash" command before running the installer. To see the symptoms when the incorrect patch is applied, see the following:

<Note 390623.1> Relinking Errors When Patching An Oracle10g Application Server 10.1.2 Infrastructure Database From 10.1.0.4.2 to 10.1.0.5.0

Microsoft Windows 2003 (AMD64/EM64T)

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.

Step 2: Test Success of Oracle Database Server 10.1.0.5 Patchset

If applying Oracle Database Patchset 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 within the following document:

<Note 359362.1> Known Issues With DB 10.1.0.5 Patchset to AS 10.1.2 homes

Step 3: Upgrade to Oracle Portal 10.1.4.0

The 10.1.2.3 Patchset updates Oracle Portal to version 10.1.4.2 only if Oracle Portal has been previously updated to 10.1.4.0. If using Oracle Portal, it is recommended to update Portal to 10.1.4.0 before applying 10.1.2.3 Patchset. If Oracle Portal is upgraded to version 10.1.4.0 after the 10.1.2.3 Patchset, the 10.1.2.3 Patchset should be run a second time to detect the required 10.1.4.x in order to perform the 10.1.4.2 upgrade. (Note the 10.1.2.2 Patchset contained the 10.1.4.1 upgrade with the same concept).

Portal 10.1.4 Information
[ http://www.oracle.com/technetwork/middleware/ias/upgrade-1014-082743.html ]

To find current version of Portal;
SQL> select version from portal.wwc_version$;

<Note 262623.1> Upgrade Note: "Primary Note for OracleAS Portal Upgrade Issues

Step 4: Apply Latest Oracle Application Server 10.1.2.3 Patchset

Apply Oracle AS 10g Patchset 3 (10.1.2.3) - <Patch:5983622> - Follow its readme for all instructions and also the following document which details any post-release documentation errata:

<Note 555681.1> Oracle Application Server Patch Set Notes Addendum 10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0)

See also:
<Note 795143.1> Understanding How AS 10g Patch Sets Update the AS Metadata Repository

Windows, see also:
<Note 434740.1> Valid Port Ranges Are Incorrect In The Documentation

Prepare for the following potential issues:

<Note 1134259.1> Applying Any Patch Set 10.1.x.x Fails During Configuration Assistant "Run One-Off Opatches"
<Note 843239.1> ADMN-100015 and Error Loading apachemoduleossl.dll After SSL Configuration or During 10g Patch Sets

Step 5: Install Latest OUI and OPatch to all Oracle Application Server homes

Obtain the latest OUI 10.1.0.6 <Patch 6640838> and apply this according to the readme and/or <Note 565374.1>. This will update the OUI files and replace OPatch to version 1.0.0.0.62, allows an overlay feature in conjunction with the OPatch utility when applying future one-off patches, and it covers a security fix which is included in Critical Patch Update documentation. Since this needs to be applied to all 10.1.2.3 ORACLE_HOMEs, you may choose to apply this to all homes in succession as one action plan.

On platforms where there has been a newer certification with Oracle Application Server 10g Release 2 (10.1.2), the Patch 6640838 installer may fail on pre-requisite checks. To workaround this, use "./runInstaller -ignoreSysPreReqs" when starting the installer. This includes RHEL5, OEL5, SLES10, HP10.31.

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.0.0.0 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 to provide a 1.0.0.0.63+ version.

For more OPatch information, see <Note 283367.1> OPatch for Oracle Application Server 10g (10.1.2, 10.1.3, 10.1.4)

On Solaris 10, OPatch may report validation errors, requiring Sun Patch 123908-01 to resolve. Please see the following My Oracle Support Document for more information:

<Note 4967132.8> Bug 4967132 - Sol: Using "opatch" on Solaris 10 Reports Validation Errors

Step 6: Address Known Issues After 10.1.2.3 Patchset

Ensure you have reviewed the Release Notes and Release Notes Addendum, as there are known issues which have been discovered after the release of the patchset.

<Note 555681.1> Oracle Application Server Patch Set Notes Addendum 10g Release 2 (10.1.2) Patch Set 3 (10.1.2.3.0)

In addition, below is a list of other known issues for which you can check depending on your usage and address accordingly.

Generic

<Note 560368.1> "Forbidden" Error After Applying Oracle Application Server 10g Patch Set
<Note 1134259.1> Applying Any Patch Set 10.1.x.x Fails During Configuration Assistant "Run One-Off Opatches"
<Note 843239.1> ADMN-100015 and Error Loading apachemoduleossl.dll After SSL Configuration or During 10g Patch Sets

SSL

IMPORTANT: The bullets below this for SSL issues will remain for past reference, but as of April 12, 2011, customers should plan on applying the latest Critical Patch Update for 10.1.2.3 as per the following document included with CPUApr2011:

<Note 1301699.1> How the SSL/TLS Renegotiation Protocol Change Affects Oracle HTTP Server
Apply <Patch 4700543>, <Patch 6370967>, and <Patch 4601861> for SSL issues within the 10.1.0.5 networking client. Note one or more of these may be applied by the Patch Set or a Critical Patch Update you plan to apply in the future.

Reference:
<Note 739725.1> IE Browser Cannot Display Page after SSL Certificate is Configured
<Note 470123.1> TLS 1.0 Handshake Fails When Using Internet Explorer On Windows Vista
<Note 457557.1> Oracle HTTP Server Startup Fails With nzos_SetIOSemantics referenced symbol not found
<Note 1177575.1> Internet Explorer Browser Clients Return 'Cannot Display The Web Page" if Client Certificate is Required

Important - Windows Only:

Most SSL fixes, including those from the above documents, are within the 10.1.0.5 codeline and need 10.1.0.5-based fixes. These can be applied to 10.1.2.x environments. On Windows, 10.1.0.5-based fixes are delivered in a cumulative bundle patch. Since it is recommended to have these, later in this document there is a step to apply the Critical Patch Update. When you apply the Critical Patch Update for 10.1.2.3 on Windows, you will be applying the latest 10.1.0.5-based bundle which is certified/tested/supported for 10.1.2.3 homes.

When the 10.1.2.3 Patch Set is applied, a minimal 10.1.0.5 Patch 13 (<Patch 5907304>) is applied and covers the above SSL issues. If this fails to apply, the following will occur:

<Note 843239.1> ADMN-100015 and Error Loading apachemoduleossl.dll After SSL Configuration or During 10g Patch Sets

Oracle Internet Directory / Single Sign-On

After patching, log into the Metadata Repository and run the ORACLE_HOME/rdbms/admin/utlrp.sql as SYS to recompile all objects. If 15 objects still remain uncompiled (using sql command, "select comp_id,version,status from app_registry;" showing OID invalid), see the following documents for instructions to complete the OID requirements:

<Note 579835.1> Stored Procedures From 10.1.2.3 Patch Cannot be Compiled
<Note 374304.1> Oid Shows Status Invalid In dba_registry and app_registry tables
<Note.730360.1> Referential Integrity in Oracle Internet Directory Version 10.1.2.3

Oracle Web Cache

If using Oracle Web Cache for load balancing:

<Note 462228.1> Web Cache Removes The Secure Flag From Cookies

Note: This is now covered with a Web Cache Bundle Patchset, listed in next step/section of this document.
If using Oracle Web Cache and SSL:

<Note 1075633.1> Internet Explorer On Windows Vista / Windows7 Fails To Connect To WebCache With SSL Protocol If SSLv2.0 Is Unchecked
<Note 342626.1> Internet Explorer Fails To Connect To Web Cache Via SSL If SSLV2.0 Is Unchecked - NZE-29048

PL/SQL Gateway (mod_plsql)

After applying 10.1.2.3 Patch Set, check your PL/SQL Toolkit version in all databases accessed by mod_plsql by issuing "select OWA_UTIL.GET_VERSION from DUAL;" as SYS. If this does not return "10.1.2.0.4", then install the new version by running $OH/Apache/modplsql/owa/owaload.sql as SYS. (This is filed as Bug 7237920).

Oracle HTTP Server

Apply <Patch:6490362> WRONG HTTP VERSION AFTER APPLYING 10.1.2.3 PATCH

(only available on limited platforms until Backport Requests are filed)

OC4J / Java

The AS 10.1.2.3 Patchset will update the JDK to version JDK 1.4.2_14 (which may vary by platform). If you have previously updated to a newer 1.4.2_xx version, you should perform this update again. You can check your version with an ORACLE_HOME/jdk/java -version" command before and after the patchset installation, (backing up the previous ORACLE_HOME/jdk, if desired). <Patch:8453300> provides the latest JDK 1.4.2_xx for platforms previously supplied from sun.com

Oracle Forms

<Note 1058514.1> Forms Servlet (frmsrv.jar) Not Updated After Patching to 10.1.2.3

Linux Only

<Note 1232573.1> Requirement to Apply 10.1.0.5 Patch Set to 10.1.2.3 Middle-Tier Homes on Linux

HP Itanium Only

In order to complete the 10.1.2.3 requirements, <Patch:7628869> (10.1.2.3.1) needs to be applied after successful completion of <Patch:5983622>. This needs to be applied before any other patching. Note that Patch 7628869 supersedes 7344601. If 7344601 is applied, now apply <Patch 7628869>.
The 10.1.2.3 Patch Set was intended to apply 10.1.0.5 client side updates to a middle-tier home, but fails to catch them all. For this reason the 10.1.0.5 Patch Set (<Patch 4505133>) need to be downloaded and applied to the middle-tier home (it would have already been applied to the Infrastructure before 10.1.2.3). It is ok to apply in reverse order, the installer only applies required updates based on installed components.
<Note 306705.1> opmnctl Generates Internal Error Message 684 Could Not Be Found In The msb File.

AIX Only

<Note 747493.1> SQL*Plus Banner Still Shows Version 10.1.0.4.2 After Application Server Patch Set
<Note 1409114.1>Cloning OracleAS FRServices Middle Tier Fails After 10.1.2.3 Patchset

Step 7: Apply Oracle Web Cache Bundle

If using Oracle Web Cache, there are separate patches made available called Bundle Patches. These are cumulative. You should apply the latest available for your platform:

10.1.2.3.1 (Bundle Patch 1) - <Patch:7438911>
10.1.2.3.2 (Bundle Patch 2) - <Patch:8402457>

If available on your platform, apply <Patch:9390733> instead of Patch 8402457 in order to resolve the following issue:

<Note 1088403.1> Oracle Webcache Crashes When Custem Log Format Uses x-protocol After Bundle Patch 10.1.2.3.2
("HTTP request-header parsing error - malformed request line" in the logs when starting)

Note:
Bundle Patches are not available on all platforms. Where there were many individual fixes made available on given platforms, a bundle was created to include them all. Other platforms may not have the fixes backported or they were not applicable to the platform. Refer to the readme for the individual fixes included.

Step 8: Apply Oracle Forms Bundle

If Oracle Forms is installed, follow the below document for the latest recommend patches:

<Note 1188127.1> Oracle Forms 10.1.2.3 Bundle Patch Frequently Asked Questions (FAQ)

Apply <Patch 7410076> to get the latest JInitiator 1.3.1.30

Step 9: Apply Oracle Reports Bundle

If Oracle Reports is installed, follow the below document for the latest recommend patches:

<Note 1162562.1> Oracle Reports - Recommended Patch Bundle on Top of 10.1.2.3

Step 10: Critical Patch Updates

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. Look for the latest update, and an associated Oracle Fusion Middleware Patch Availability Document, which will contain the latest patches to apply to your Oracle Application Server 10g Release 2 (10.1.2) homes:

Critical Patch Updates (CPU) and Security Alerts
[ http://www.oracle.com/technology/deploy/security/alerts.htm ]

Check for latest Advisory and within are links to obtain patches

An Advisory documents the vulnerabilities for a CPU release.

A Patch Availability Document provides the cumulative patches for each product version within Lifetime Support as defined by Error Correction policies.

Because 10.1.2.3 is no longer under error correction support, the last Critical Patch Update consideration for this version was in October 2011. The following is the October 2011 Patch Availability Document:

<Note 1346104.1> Patch Set Update and Critical Patch Update October 2011 Availability Document

The below document can be used to provide more information on the patching process and examples in a step-by-step format:

<Note 405972.1> Oracle Application Server 10g Examples for Critical Patch Updates - Plus FMW11g

Windows Only:

After the initial Oracle Database 10.1.0.5.0 Patchset is applied to an Infrastructure or middle-tier, (via DB Patchset or AS Patchset in middle-tier-homes), there may be a reason to update the installed 10.1.0.5.0 components. On Windows, this is a cumulative patch referred to as '10.1.0.5 Patch x'. If you have one of these applied, it may conflict with Critical Patch Updates (CPU). You should always apply the latest CPU, which will include the previous '10.1.0.5 Patch x' fixes. Ignore any OPatch "conflict" message in this case.

Important:
In normal circumstances, you should only need to apply the CPU for 10.1.2.3 to obtain the 10.1.0.5 fixes. The below documents outline the 10.1.0.5 bundles as they are released separate from the CPUs. Applying the CPU for 10.1.2.3 is the only tested/certified/supported method obtain the 10.1.0.5-based bundle patches.

Reference:
<Note 161549.1> Oracle Database Server and Networking Patches for Microsoft Platforms
<Note 276548.1> 10.1.0.x Oracle Database and Networking Patches for Microsoft Platforms

Step 11: Update JDK to Latest 1.4.2_xx

For some known Java issues, it is recommended to download <Patch 8453300> to update the ORACLE_HOME/jdk directory with a newer 1.4.2_xx release. My Oracle Support can only supply this Java version for Sun, Linux and Windows platforms. Other platforms must obtain the newer JDK from the operating system vendors. The following documents provide more information about this:

<Note 360870.1> Impact of Java Security Vulnerabilities on Oracle Products
<Note.952075.1> Java SE (J2SE) End of Life and Oracle Fusion Middleware Policy
<Note 272808.1> How to update the default JDK installed in Application Server 9.0.4 and 10.1.2

Step 12: Daylight Saving Time Updates

If you have followed this document entirely, you will have most Daylight Saving Time updates. The 10.1.2.3 Patch Set will provide some within the 10.1.0.5 area, as will the Critical Patch Update. There may be newer updates, but would depend on the Oracle Database Server used. Obtain newer Daylight Saving Updates for the Oracle Database Server product. For the Oracle Application Server 10g, there is more of a need to update the JDK (the previous step) to obtain these updates for custom Java applications and other Oracle applications such as AS Control and DB Control, which are built on Java technologies. For more information see the following: