Sunteți pe pagina 1din 120

Oracle® Application Server and Oracle Developer Suite

Patch Set Notes 10g Release 2 (10.1.2) Patch Set 2 (10.1.2.2.0) for Linux x86 and Linux x86-64

Decemeber 2006

This document contains the following sections:

Section 1, "Introduction"

Section 2, "Patch Set Overview"

Section 3, "Patch Set Documentation"

Section 4, "Patch Set Requirements"

Section 5, "Before You Apply This Patch Set"

Section 6, "Patch Application for Oracle Collaboration Suite Environments"

Section 7, "Patch Set Application"

Section 8, "Postapplication Considerations"

Section 9, "Known Issues"

Section 10, "Patch Set Components"

Section 11, "Documentation Accessibility"

1 Introduction

This document accompanies Oracle Application Server and Oracle Developer Suite 10g Release 2 (10.1.2) Patch Set 2 (10.1.2.2.0) (OracleAS 10g Release 2 Patch Set 2). This patch set is applicable for the following releases only:

Oracle Application Server 10g Release 2 (10.1.2.0.0)

Oracle Application Server 10g Release 2 Standard Edition One (10.1.2.0.1)

Oracle Application Server 10g Release 2 (10.1.2.0.2)

Oracle Application Server Forms and Reports Servics (10.1.2.0.2)

Oracle Developer Suite 10g (10.1.2.0.2)

OracleAS 10g Release 2 Patch Set 1 (10.1.2.1.0)

Oracle Application Server Portal 10g Release 2 (10.1.4)

Oracle Business Intelligence Tools 10g Release 2 (10.1.2)

Oracle Business Intelligence Tools 10g Release 2 (10.1.2.0.2)

Oracle Business Intelligence 10g Release 2 (10.1.2)

Oracle Business Intelligence 10g Release 2 (10.1.2.0.2)

Oracle Business Intelligence 10 g Release 2 (10.1.2) ■ Oracle Business Intelligence 10 g Release 2

Oracle Business Intelligence Tools 10g (10.1.2.0.2) that shipped as part of Oracle Developer Suite 10g Release 2 (10.1.2)

Note:

Linux x86 and Linux x86-64 are referred to as Linux in the

document.

2

Patch Set Overview

Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality. Patch sets contain generic fixes that apply to all platforms and may also include platform-specific fixes.

Patch sets include all files that have been rebuilt to implement the bug fixes in the set. All of the fixes in the patch set have been tested and are certified to work with one another. Because this patch set includes only low impact fixes, you are not required to certify applications or tools against the server (unless specifically instructed by your software vendor).

This patch set is cumulative and includes all of the fixes from OracleAS 10g Release 2 Patch Set 1 (10.1.2.1.0). It can be applied to any of the instances listed in Section 1, "Introduction" as well as any of those instances that have OracleAS 10g Release 2 Patch Set 1 (10.1.2.1.0) already applied.

Note:

If this patch set is applied against an OracleAS Portal 10.1.4

repository, the repository will be upgraded to 10.1.4.1.

The OracleAS 10g Release 2 Patch Set 2 updates the software on all applicable Oracle Application Server installations (refer to the top of Section 1, "Introduction" for a list of applicable releases). If you have a Portal and Wireless installation, you must also use this patch set to update your OracleAS Metadata Repository.

This patch set is not a complete software distribution. You must install this patch set over one of the releases identified in Section 1, "Introduction".

Refer to the installation guide and release notes for the base requirements for your Oracle product, and to confirm that all required patches have been installed on your system.

To download free installation documentation, release notes, white papers, or other collateral, go to Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at:

http://www.oracle.com/technology/membership

If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at:

http://www.oracle.com/technology/documentation

The following sections provide further information about the OracleAS 10g Release 2 Patch Set 2:

Section 2.1, "Supported Database Versions"

Section 2.2, "Software Update"

Section 2.3, "Metadata Repository Update"

For a list of products included in this patch set, see the Section 10, "Patch Set Components".

2.1 Supported Database Versions

This patch set includes three updates: the Software Update, the Metadata Repository Update, and the Oracle Database 10g Release 1 (10.1.0.5) patch set. Oracle Database 10g Release 1 (10.1.0.5) is the minimum database release required by OracleAS 10g Release 2 Patch Set 2. Note the following:

The Oracle Database 10g Release 1 (10.1.0.5) patch set must be applied to all databases containing a Metadata Repository before OracleAS 10g Release 2 Patch Set 2 is applied.

If you have previously installed Oracle Application Server 10g Release 2 (10.1.2) with Oracle Database version 9.2.0.6, you must first upgrade to Oracle Database version 9.2.0.7.

If your database version is 9.2.0.7 or 10.2, then the Oracle Database 10.1.0.5 database patch is not required. Also, the Metadata update for upgrading the Metadata Repository should be run from the middle tier.

2.2 Software Update

Application of the OracleAS 10g Release 2 Patch Set 2 Software Update (Software Update) updates the software and configuration files contained in your Oracle Application Server middle-tier and infrastructure Oracle home directories. Oracle home is the full path of the Oracle directory that contains the Oracle Application Server installation. $ORACLE_HOME will be used in this documentation to refer to the directory where the product is installed.

Note:

ORACLE_HOME should be replaced with the full path of

the installed Oracle Application Server instance.

The installer used for the Software Update automatically determines which set of software patches is appropriate for your installation.

The order of application of the Software Update to your middle tier and infrastructure installation does not matter. However, the following should be noted:

You must apply the Software Update to each of your existing middle-tier installations before you apply the OracleAS 10g Release 2 Patch Set 2 Metadata Repository Update to the Metadata Repository used by each of the existing middle-tiers.

If you will be adding additional middle-tier installations to the updated Metadata Repository at a later time, you must apply the Software Update to the middle-tiers that will be using the Metadata Repository.

Back up the relevant Metadata Repository before applying the Software Update.

For example, a distributed Oracle Application Server environment may be set up as follows:

Computer 1 contains Oracle Identity Management Services including Oracle Internet Directory, Oracle Directory Integration and Provisioning, Oracle Delegated Administration Services, Oracle Application Server Single Sign-On (OracleAS Single Sign-On), Oracle Application Server Certificate Authority (OracleAS Certificate Authority).

Computer 2 contains the OracleAS Metadata Repository.

Computer 3 contains an Portal and Wireless instance.

Computer 4 contains an J2EE and WebCache instance.

Computers 3 and 4, respectively, share the same Oracle Application Server Infrastructure which exists collectively on Computers 1 and 2.

All of the computers in the environment require application of the Software Update.

For this type of environment, the updates could be installed as follows:

1. Apply the Oracle Database 10g Release 10.1.0.5 Patch Set on computers 1 and

2.

2. Apply the Software Update to the middle tier installations on computers 3 and 4.

3. Apply the Software Update to computers 1 and 2.

4. Apply the Metadata Repository Update to Computer 2 using one of the middle tier installations on computers 3 or 4.

2.3 Metadata Repository Update

The Metadata Repository Update updates the software schemas in the Metadata Repository that are used by all of your Oracle Application Server middle tier installations. It also updates the binaries for Oracle Application Server Backup and Recovery Tool and the Oracle Application Server Guard used in Metadata Repository only installations.

You can apply the Metadata Repository Update patch to a middle tier Oracle home or to an infrastructure Oracle home containing both Oracle Identity Management and OracleAS Metadata Repository. Use the same Oracle home for future Metadata Repository patch updates. The Metadata Repository Update only needs to be applied once per Metadata Repository.

Back up the relevant database before applying the Metadata Repository Update.

During application of the Metadata Repository Update, the installer validates the ORACLE_HOME/config/ias.properties file to verify that the Oracle home you have designated on the installation screen is either a middle tier using Oracle Identity Management Services, or an Oracle Identity Management installation with an OracleAS Metadata Repository.

You must apply the Software Update to each of your middle-tier installations before you apply the Metadata Repository Update to the Metadata Repository used by each of the middle tiers.

3 Patch Set Documentation

The documents below are related to this release of the Oracle Application Server patch set:

Oracle Application Server and Oracle Developer Suite Patch Set Notes 10g Release 2 (10.1.2) Patch Set 2 (10.1.2.2.0) for Linux x86 and Linux x86-64 (this document). It provides the following information:

All system requirements and instructions needed to install or deinstall the patch set itself.

A list of known issues related to operating the OracleAS 10g Release 2 Patch Set 2.

This document is contained in the file

/Disk1/doc/readme.html in the patch set distribution.

Oracle Application Server and Oracle Developer Suite List of Bugs Fixed 10g Release 2 (10.1.2) Patch Set 2 (10.1.2.2.0). It provides a list of all generic (common to all operating systems) bugs related to Oracle Application Server that have been fixed in this release sorted, by product group.

This document is contained in the file

/Disk1/doc/bugsfixed.html in the patch set distribution.

These documents are also available on OracleMetaLink (http://metalink.oracle.com). Check document 329361.1, Oracle Application Server 10g Release 2 Support Status and Alerts for information.

To locate document 329361.1:

1. Click Advanced at the top of the OracleMetaLink page.

2. Enter 329361.1 in the Document ID field, and click Submit.

4 Patch Set Requirements

Refer to your installation guide and release notes for the base requirements for your system.

Note:

If your system does not meet one of the minimum

requirements listed in this section, then log a service request to request assistance with this patch set.

4.1 Required Software

The following is a list of the required system software that must be installed before installing this patch set:

One of the baseline releases identified in Section 1, "Introduction".

To check the release number of your Oracle Application Server instance, go to the Home page of the Oracle Application Server Control Console and click About Oracle Enterprise Manager 10g Application Server.

One of the following supported operating systems:

Oracle Application

Supported Operating System

Oracle Application Server 10g Release 2 (10.1.2.0.0)

The following operating systems are supported on Linux x86:

Red Hat Enterprise Linux AS/ES 2.1 Systems

Red Hat Enterprise Linux AS/ES 3.0 Systems

Red Hat Enterprise Linux AS/ES 4.0 Systems

SUSE Linux Enterprise Server 8 Systems

SUSE Linux Enterprise Server 9 Systems

The following operating systems are supported on Linux x86-64:

Red Hat Enterprise Linux AS/ES 3.0 Systems

SUSE Linux Enterprise Server 9 Systems

Oracle Application Server 10g Release 2 (10.1.2.0.1) Standard Edition One

The following operating systems are supported on Linux x86:

Red Hat Enterprise Linux AS/ES 2.1 Systems

 

Red Hat Enterprise Linux AS/ES 3.0 Systems

SUSE Linux Enterprise Server 8 Systems

SUSE Linux Enterprise Server 9 Systems

The following operating systems are supported for Linux x86-64:

Red Hat Enterprise Linux AS/ES 3.0 Systems

SUSE Linux Enterprise Server 9 Systems

Oracle Application Server 10g Release 2 (10.1.2.0.2)

The following operating systems are supported on Linux x86:

OracleAS Portal 10.1.4

Red Hat Enterprise Linux AS/ES 2.1 Systems

Red Hat Enterprise Linux AS/ES 3.0 Systems

Red Hat Enterprise Linux AS/ES 4.0 Systems

SUSE Linux Enterprise Server 8 Systems

SUSE Linux Enterprise Server 9 Systems

The following operating systems are supported on Linux x86-64:

Red Hat Enterprise Linux AS/ES 3.0 Systems

Red Hat Enterprise Linux AS/ES 4.0 Systems

SUSE Linux Enterprise Server 9 Systems

Oracle Application Server 10g Release 2 Patch Set 1 (10.1.2.1.0)

For a list of supported operating systems, please refer to the OracleAS 10g Release 2 Patch Set 1 (10.1.2.1.0) readme.

Oracle Application

Supported Operating System

Oracle Developer Suite 10g

The following operating systems are supported on Linux x86:

(10.1.2.0.2)

Red Hat Enterprise Linux AS/ES 2.1 Systems

Red Hat Enterprise Linux AS/ES 3.0 Systems

Red Hat Enterprise Linux AS/ES 4.0 Systems

SUSE Linux Enterprise Server 8 Systems

SUSE Linux Enterprise Server 9 Systems

The following operating systems are supported on Linux x86-64:

Red Hat Enterprise Linux AS/ES 3.0 Systems

Red Hat Enterprise Linux AS/ES 4.0 Systems

SUSE Linux Enterprise Server 9 Systems

Oracle Business Intelligence 10g Release 2 (10.1.2)

The following operating systems are supported on Linux x86:

Red Hat Enterprise Linux AS/ES 2.1 Systems

Red Hat Enterprise Linux AS/ES 3.0 Systems

Red Hat Enterprise Linux AS/ES 4.0 Systems

SUSE Linux Enterprise Server 8 Systems

SUSE Linux Enterprise Server 9 Systems

The following operating systems are supported on Linux x86-64:

Red Hat Enterprise Linux AS/ES 3.0 Systems

SUSE Linux Enterprise Server 9 Systems

Oracle Business Intelligence 10g Release 2 (10.1.2.0.2)

The following operating systems are supported on Linux x86:

Red Hat Enterprise Linux AS/ES 2.1 Systems

Red Hat Enterprise Linux AS/ES 3.0 Systems

Red Hat Enterprise Linux AS/ES 4.0 Systems

SUSE Linux Enterprise Server 8 Systems

SUSE Linux Enterprise Server 9 Systems

The following operating systems are supported on Linux x86-64:

Red Hat Enterprise Linux AS/ES 3.0 Systems

Red Hat Enterprise Linux AS/ES 4.0 Systems

SUSE Linux Enterprise Server 9 Systems

4.2 Preinstallation Requirements

The following list is the preinstallation requirements for this patch set:

Ensure the system configuration meets the recommended system configuration described in your documentation.

Back up your Oracle software and inventory before applying this patch set, or before making any other changes to your existing Oracle software. Refer to your administrator’s guide for instructions on backing up your Oracle software and inventory.

Back up the relevant database before applying the Software Update to an Oracle Identity Management installation. Refer to your administrator’s guide for instructions on backing up your database.

Backup up the OracleAS Metadata Repository before applying the Metadata Repository Update.

5

Before You Apply This Patch Set

Read this section before applying this patch set to determine whether any of the following topics apply to your Oracle system. Follow the instructions in the topic before proceeding with installation of this patch set.

This section includes the following notes:

Section 5.1, "Stop all Oracle Developer Suite Processes and Programs"

Section 5.2, "OracleAS Infrastructure Must be Running During Software Update"

Section 5.3, "Setting and Unsetting Environment Variables"

Section 5.4, "Configure Virtual Server Names and Ports for the Load Balancer in a High Availability Environment."

Section 5.5, "Applying the Oracle Database 10g Release 1 (10.1.0.5) Patch Set"

Section 5.6, "Installing the Patch Set to a Distributed Configuration Management Cluster"

Section 5.7, "Software Update to a File-based Repository"

Section 5.8, "OracleAS Wireless Developer Kit does not Work with XHTML MP Devices"

Section 5.9, "Stopping an Edge Job for OracleAS Wireless"

Section 5.10, "Stopping Sensor Edge Server"

Section 5.11, "Upgrading an Earlier Release of Oracle Application Server"

Section 5.12, "Enable Components Prior to Patch Application"

Section 5.13, "Preparing for an Oracle Internet Directory Multimaster Replication Update"

Section 5.14, "Oracle Directory Integration and Provisioning and Oracle Internet Directory"

5.1 Stop all Oracle Developer Suite Processes and Programs

If you are running Oracle Developer Suite, you must stop all processes and programs that are running from your Oracle Developer Suite instance before applying this software patch.

5.2 OracleAS Infrastructure Must be Running During Software Update

When you apply the Software Update to an Oracle Application Server middle-tier or an OracleAS Infrastructure Oracle home, the following must be up and running of the infrastructure instance:

OracleAS Metadata Repository’s listener

Database containing OracleAS Metadata Repository

Oracle Internet Directory

5.3 Setting and Unsetting Environment Variables

The operating system user who will be installing this patch set should read Section 4.9, "Environment Variables," in the Oracle Application Server Installation Guide before performing the patch installation.

This section contains important information about the environment variables that need to be set or unset prior to performing the installation.

5.4 Configure Virtual Server Names and Ports for the Load Balancer in

a High Availability Environment.

If you have a configuration where the LDAP port numbers on the LDAP load balancer (for example, 389 for non-SSL and 636 for SSL) map to but are different from the physical LDAP port numbers on the OID node (for example, 1030 for non-SSL and 1040 for SSL), you must change the physical LDAP ports on the OID nodes to match the LDAP ports configured on the LDAP load balancer before you install OracleAS 10g Release 2 Patch Set 2.

To do this:

1. Change the values of orclnonsslport and orclsslport in the following entry:

"cn=configset0,cn=osdldapd,cn=subconfigsubentry"

Set the orclnonsslport value to match the NONSSL LDAP port value on the load balancer and the orclsslport value to match the SSL LDAP port value on the load balancer.

2. Shutdown and restart the OID instance.

3. Install OracleAS 10g Release 2 Patch Set 2.

This procedure is required for all components other than OID.

However, if OID is located on the same machine with SSO/DAS, then this procedure is also required prior to the OID patch installation.

Note:

For more information, refer to Section 12.2.3, "Configure Virtual Server Names and Ports for the Load Balancer" in the Oracle Application Server Installation Guide.

5.5 Applying the Oracle Database 10g Release 1 (10.1.0.5) Patch Set

The Oracle Database 10g Release 1 (10.1.0.5) Patch Set must be applied to all database instances (for both the Identity Management and Metadata Repository install type and Metadata Repository only install type) before OracleAS 10g Release 2 Patch Set 2 is applied.

For more information about supported databases with OracleAS 10g Release 2 Patch Set 2, see Section 2.1, "Supported Database Versions".

5.6

Installing the Patch Set to a Distributed Configuration Management

Cluster

If you are installing this patch set to an instance belonging to a Distributed Configuration Management (DCM) cluster which contains multiple instances, then it is necessary to remove the instance from the cluster before applying the patch. Use the following command to remove the instance:

dcmctl leavecluster

This will avoid possible configuration inconsistencies between multiple instances in the cluster.

After applying the patch set to all individual standalone instances, you can restore the cluster topology by running the following command from the instances:

dcmctl joincluster -cl cluster

In the preceding command, cluster is the name of the cluster.

5.7 Software Update to a File-based Repository

If you are applying the Software Update to an Oracle Application Server cluster which uses a file-based repository, then you can apply the update to any cluster node in any order. You can apply the update in this manner as long as the repository node is not being updated at the same time as any of the cluster nodes.

5.8 OracleAS Wireless Developer Kit does not Work with XHTML MP

Devices

The OracleAS Wireless Developer Kit (WDK) does not work with XHTML MP devices.

To workaround this problem, complete the following steps:

1. Back up the following directory prior to installing the OracleAS 10g Release 2 Patch Set 2:

Solaris:

ORACLE_HOME/j2ee/OC4J_Wireless/applications/wdk/wdk-web/repository

Windows:

ORACLE_HOME\j2ee\OC4J_Wireless\applications\wdk\wdk-web\repository

2. Install the OracleAS 10g Release 2 Patch Set 2.

This will redeploy the WDK application.

3. Shut down the OC4J_Wireless process.

4. Replace the content of the following directory with the content from the previous installation which was backed up in step 1.

Solaris:

ORACLE_HOME/j2ee/OC4J_Wireless/applications/wdk/wdk-web/repository

Windows:

ORACLE_HOME\j2ee\OC4J_Wireless\applications\wdk\wdk-web\repository

5. Start the OC4J_Wireless process.

5.9 Stopping an Edge Job for OracleAS Wireless

If you are applying the Software Update to an OracleAS Wireless environment, then the edge job must be stopped before applying the update. You will need to remove the lock and clean the database. For information about the processes, refer to the OracleAS Wireless chapter in the Oracle Application Server Release Notes.

5.10 Stopping Sensor Edge Server

If you are applying the Software Update to Oracle Application Server 10g Release 2 (10.1.2.0.0), then you should stop the edge task before applying the patch set. Use the following command to stop the edge task:

exec edge.edg_utl.deschedule_job;

After applying the patch set, start the service to start receiving data, as follows:

1. Log in to the database as follows:

$Infra_Oracle_Home/bin/sqlplus /nolog

2. Connect as sysdba using the following command:

sql> connect sys/password@sid as sysdba

3. Start the edge task using the following command:

exec edge.edg_utl.schedule_job;

4. Confirm the service has started using the following command:

select component_name, status from edge.edg_jobs;

The following message should be returned:

COMPONENT_NAME:EdgeDispatchJob

STATUS:Started

5.11 Upgrading an Earlier Release of Oracle Application Server

If you have an earlier release of Oracle Application Server, then the following should be noted:

When upgrading from an Oracle9i Application Server (Oracle9iAS) 9.0.2.x or 9.0.3.x, or Oracle Application Server 10g (9.0.4.x) middle tier to an Oracle Application Server 10g Release 2 (10.1.2) middle tier, you can patch the Oracle Application Server middle tier with the Oracle Application Server 10g Release 2 (10.1.2) Patch Set 2 (10.1.2.2.0) prior to running the Oracle Application Server Upgrade Assistant. Refer to the Oracle Application Server Upgrade and Compatibility Guide for more information on the upgrade process.

When upgrading an Oracle9i Application Server (Oracle9iAS) 9.0.3.x instance to Oracle Application Server 10g Release 2 (10.1.2) patched instance, the

OracleAS Web Cache plug-in may fail. The workaround is to use Oracle9i Application Server (Oracle9iAS) 9.0.2 webcache.dtd to replace the Oracle9i Application Server (Oracle9iAS) 9.0.3 webcache.dtd. The dtd file is located in the ORACLE_HOME/webcache/dtds directory (for both 9.0.2 and 9.0.3).

5.12 Enable Components Prior to Patch Application

When applying OracleAS 10g Release 2 Patch Set 2 on an Oracle home with a disabled OC4J instance, the installer will display the following message:

Install has detected that the OC4J home instance is disabled in the ORACLE_HOME where the patchset is being installed. The OC4J home instance must be enabled first before the patchset installation can proceed. Please enable the OC4J home instance through Enterprise Manager and try installing again.

Click OK and then manually enable the instance using Oracle Enterprise Manager 10g as follows:

1. Go to the Oracle Enterprise Manager 10g home page.

2. Click Enable/Disable Components.

3. Select the disabled component in the Disabled Components listing.

4. Click Remove. The component will move to the Enabled Components listing.

5. Click OK.

Once the instance has been enabled, click Next to continue the installation. After successfully patching the instance, you can disable it.

Note:

When applying the patch using the silent installation method,

the installation will fail if the instance is disabled. The log file will indicate that the installation failed due to the disabled instance. The message will appear in English only.

To avoid this, enable the instance prior to applying the patch.

5.13 Preparing for an Oracle Internet Directory Multimaster

Replication Update

Before you begin patching Oracle Internet Directory 10.1.2.x.x in a replicated environment, you must perform the following steps. The first step should be done for all nodes in the replication group. The rest of the steps are for all replica nodes other than Master Definition Site (MDS) Replica or Primary supplier replica.

1. Delete the ORASSO.WWSEC_PERSON$ table from master and replica nodes as follows:

On the master node run the following commands:

sqlplus repadmin/password

BEGIN

DBMS_REPCAT.DROP_MASTER_REPOBJECT

(

sname =>'ORASSO', oname => 'WWSEC_PERSON$', type => 'TABLE', drop_objects => false

);

END;

/

On each node in the replication group, run the following command:

sqlplus "/ as sysdba" delete from orasso.wwsec_person$ where user_name not like '%PUBLIC'; commit;

Note:

node.

For more information, refer to Oracle Application Server High Availability Guide 10g Release 2 (10.1.2.0.2) available on Oracle Technology Network at

http://www.oracle.com/technology

The preceding steps will need to be run anytime you rectify a

2. Locate the database registration entry of the database replica to be updated using the following command:

ORACLE_HOME/bin/ldapsearch -h host -p port -D cn=orcladmin -w superuser_password -b "cn=oraclecontext" -s one "(objectclass=orcldbserver)" dn

This will return a list of Distinguished Names (DNs) corresponding to all the databases registered in Oracle Internet Directory in the following form:

cn=database_name,cn=oraclecontext

3. Locate the DN of the following entry, which will be used in Step 5 of this procedure:

cn=dbname_of_replica_to_be_updated,cn=oraclecontext

4. Identify the appropriate replica ID to be updated using the following command:

ORACLE_HOME/bin/ldapsearch -h hostname_of_replica_being_updated -p port -D cn=orcladmin -w superuser_password -b "" -s base "(objectclass=*)" orclreplicaid

5. Modify the seealso attribute of Replica Subentry for the replica to be updated as follows:

a. Create a file, for example mod.ldif, with the following contents:

#File Name : mod.ldif dn: orclreplicaid=replicaid_from_step_4,cn=replication configuration changetype: modify replace: seeAlso #The DN used in seealso attribute is obtained in Step #1. seealso: cn=dbname_of_replica_being_updated,cn=oraclecontext

b. Modify the replica subentry using ldapmodify command, as follows:

ORACLE_HOME/bin/ldapmodify -h hostname_of_replica_being_updated -p port -D superuser_DN -w superuser_password -v -f mod.ldif

5.14 Oracle Directory Integration and Provisioning and Oracle Internet

Directory

If Oracle Directory Integration and Provisioning and Oracle Internet Directory are on separate machines in an Oracle Application Server 10g Release 2 (10.1.2.0.0) environment, then the initial ORACLE_ HOME/network/admin/tnsnames.ora file on the Oracle Directory Integration and Provisioning machine is incorrect.

The connection information in the tnsnames.ora file contains the host name of the Oracle Directory Integration and Provisioning installation instead of the host name of the actual machine that has Oracle Internet Directory and the database. The host name should be changed to the host name where the database resides.

For example, if the Oracle Directory Integration and Provisioning server is located on machine ntmachine1.myco.com, and the Oracle Internet Directory and database are located on machine unixmachine2.myco.com, then the tnsnames.ora file on ntmachine1.myco.com will contain the following:

oradb = (DESCRIPTION=(ADDRESS_

LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=ntmachine1.myco.com)(PORT=1521)))

(CONNECT_DATA=(SERVICE_NAME=oradb.us.myco.com)))

This entry should be changed so the host name indicates the host with the database, such as:

oradb = (DESCRIPTION=(ADDRESS

_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=unixmachine2.myco.

com)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=oradb.us.myco.com)))

You can change the entry either by manually editing the file, or by using the network configuration tool.

6 Patch Application for Oracle Collaboration Suite Environments

Oracle Collaboration Suite customers should review the current Oracle Collaboration Suite Release Notes before applying any Oracle Application Server patches. The documentation is available at

http://www.oracle.com/pls/cs101/homepage

7 Patch Set Application

This section contains the following topics:

Section 7.1, "Applying OracleAS 10g Release 2 Patch Set 2"

Section 7.2, "Applying OracleAS 10g Release 2 Patch Set 2 on OracleAS Cluster (Identity Management) Environments"

Section 7.3, "Installing OracleAS 10g Release 2 Patch Set 2 on Distributed OracleAS Cluster (Identity Management) Environments"

Section 7.4, "Applying OracleAS 10g Release 2 Patch Set 2 on OracleAS Portal 10.1.4 to Upgrade to OracleAS Portal 10.1.4.1"

Section 7.5, "Applying OracleAS 10g Release 2 Patch Set 2 on Oracle Developer Suite"

Section 7.6, "Silent and Non-Interactive Patch Application"

Section 7.7, "Failure During Software Update"

7.1 Applying OracleAS 10 g Release 2 Patch Set 2

This section describes application procedures for the OracleAS 10g Release 2 Patch Set 2. It includes the following steps:

Section 7.1.1, "Back up Your Existing Environment"

Section 7.1.2, "Apply the Oracle Database Update"

Section 7.1.3, "Apply the OracleAS 10g Release 2 Patch Set 2 Software Update"

Section 7.1.4, "Apply the Metadata Repository Update"

Section 7.1.5, "Update OracleAS Portal Repositories that Reside in Oracle RAC Manually"

Section 7.1.6, "Update OracleAS Portal Repository Manually"

Section 7.1.7, "Update OracleAS Wireless Repository Manually"

7.1.1 Back up Your Existing Environment

There is no automatic procedure for deinstalling the OracleAS 10g Release 2 Patch Set 2. Oracle recommends that you make a backup of your existing environment before you install OracleAS 10g Release 2 Patch Set 2. If you choose to remove OracleAS 10g Release 2 Patch Set 2, or if you encounter a problem with application of the patch, then you can restore your original environment.

See Also:

Oracle Application Server 10g Release 2 (10.1.2)

installation guide for complete deinstallation procedure.

7.1.2 Apply the Oracle Database Update

If you plan to update Metadata Repository for Oracle Identity Management with Metadata Repository or Metadata Repository for 10.1.2 release only environments then you must first apply the patch for bug 4432964 and then apply the Oracle Database 10g Release 1 (10.1.0.5) patch set.

The database patch is available in the following file:

p4505133_10105_LINUX.zip

After unzipping the file, the patch is available in the Database_Patchset_ 10.1.0.5_linux directory.

The following procedure describes how to apply the patch to a Metadata Repository that was created as part of the Infrastructure installation with Oracle Universal Installer.

If you installed a Metadata Repository into an existing

database using the Oracle Application Server Metadata Repository Creation Assistant, or you are using Oracle Real Application Clusters, then refer to Oracle Database Patch Set Notes (for Oracle Application Server and Oracle Collaboration Suite) 10g Release 1 (10.1.0.5) for instructions. The database patch set notes are available in the following directory:

ORACLE_HOME/rdbms/notes

Note:

1. Log in to the system.

Log in as the oracle user.

2. Set the display for the local system using the following command, if you are not installing the software on the local system.

Bourne, Bash or Korn shell:

$ DISPLAY=local_host:0.0 ; export DISPLAY

C shell:

% setenv DISPLAY local_host:0.0

In the preceding commands, local_host is the host name or IP address of the system that you want to display Oracle Universal Installer screens.

3. Stop all listener, agent and processes running in or against the Oracle home as follows:

Stop the processes.

$ORACLE_HOME/opmn/bin/opmnctl stopall

Stop Oracle Enterprise Manager 10g.

Run the following two commands:

$ORACLE_HOME/bin/emctl stop iasconsole $ORACLE_HOME/bin/emctl stop dbcontrol

Shut down the existing Oracle instance using normal or immediate priority using one of the following commands:

For normal shutdown:

SQL> SHUTDOWN;

For immediate shutdown:

SQL> SHUTDOWN immediate;

Stop the database listener.

$ORACLE_HOME/bin/lsnrctl stop

4. Enter the following command to start Oracle Universal Installer:

$ cd /tmp

$ /directory_location/runInstaller

In the preceding commands, directory_location is the directory with the database patch set files.

5. Click Next on the Welcome screen.

6. Click Browse on the Specify File Locations screen. It is next to the Path field in the Source section.

7. Select the products.xml file from directory where you put the patch files.

8. Click Next.

9. Select the Oracle home that will get the update in the Name field.

10. Click Next.

11. Click Install.

Note:

If you are installing the patch on Unix based systems, then you

will have to run the root.sh script in a separate window when prompted by the system. Run the script as the root user.

12. Click Exit when the End of Installation screen appears.

13. Click Yes to exit from Oracle Universal Installer.

14. Start the Oracle instance using the following commands:

SQL> connect SYS as SYSDBA SQL> startup

15. Set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB, if using a server parameter file. Log in as the sys user and use the following command to check the parameter:

SQL> show parameter SHARED_POOL_SIZE

If the parameter is not at least 150 MB, then use the following command to set it:

SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;

16. Set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB, if necessary. Log in as the sys user and use the following command to check the parameter:

SQL> show parameter JAVA_POOL_SIZE

If the parameter is not at least 150 MB, then use the following command to set the parameter:

SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;

17. Shut down the database using the following command:

SQL> SHUTDOWN

18. Enter the following SQL*Plus commands:

SQL> STARTUP UPGRADE SQL> SPOOL patch.log SQL> @/ORACLE_HOME/rdbms/admin/catpatch.sql

SQL> SPOOL OFF

19. Review the patch.log file for errors and inspect the list of components that is displayed at the end of the catpatch.sql script. This list provides the version and status of each SERVER component in the database.

20. If necessary, re-run the catpatch.sql script to correct any problems.

21. Restart the database as follows:

SQL> SHUTDOWN

SQL> STARTUP

22. Run the utlrp.sql script as the sys user to recompile all invalid PL/SQL packages. Use the following command to run the script:

SQL> @/ORACLE_HOME/rdbms/admin/utlrp.sql

7.1.3 Apply the OracleAS 10 g Release 2 Patch Set 2 Software Update

The Software Update updates the software and configuration files contained in the Oracle home.

For middle-tier installations, the Software Update may also upload data specific to the middle-tier installation you are updating to the OracleAS Metadata Repository.

For Oracle Identity Management installations, the Software Update also updates the schemas in the Identity Management system.

Note:

When applying the software update to an Oracle home that

contains only OracleAS Metadata Repository, all Identity Management and middle tier processes should be stopped prior to applying the software update.

When the Software Update is applied to an infrastructure Oracle home, it is referred to as an Identity Management Update in these notes.

Note:

If you are running an installation that does not require an

infrastructure database, then you only need to apply the Software Update portion of this patch set. No other updates are required.

The following procedure describes how to apply the Software Update:

1. Back up the relevant OracleAS Metadata Repository before applying the Software Update.

2. Oracle Universal Installer is used to update the Oracle Application Server software. Start the Oracle Universal Installer that comes with the OracleAS 10g Release 2 Patch Set 2 as follows:

> ./runInstaller

3. Table 1 describes the steps and screens you will encounter during application of the Software Update on an Oracle Application Server middle-tier, OracleAS Infrastructure, or Oracle Business Intelligence installations.

Table 1

Steps for Applying Oracle Application Server Patch

Screen

Action

1. Welcome

Review the Oracle Universal Installer Welcome screen and click Next.

The Welcome screen provides information about Oracle Universal Installer.

The following buttons appear on the installation screens:

Deinstall Products: Deinstall individual components or the entire product. This button appears only on the Welcome screen.

About Oracle Universal Installer: View the version number of the installer.

Help: Access detailed information about the functionality of each screen.

Installed Products: View currently installed products or deinstall the entire product or components.

Back: Return to the previous screen. This button is disabled on the Welcome screen.

Next: Proceed to the next screen.

Install: Install the selected product. This button is disabled on the Welcome screen.

Cancel: Quit the installation process and exit the installer.

2. Specify File

Locations

Check the default source path, destination name, and destination path shown on the Specify File Location page for your update of your installed Oracle Application Server software. If you do not want to use the defaults, then enter the values you want to use. Click Next to continue.

The Specify File Locations screen allows you to enter the full path for the source and destination locations for your update of Oracle Application Server software. The Name and Path fields must have the same values as the base installation.

Source: This is the full path to the products.xml file from which the product will be installed. The installer detects and uses the default values of the products.xml file of the installation program. Do not change the path.

Name: Select the Oracle home name for the environment to be patched.

Oracle homes are identified by name. The Oracle home name identifies the program group associated with a specific Oracle home and the installed Oracle services associated with the home.

Path: This is the full path to the Oracle home for application of the Software Update.

This field is filled automatically when you select the Oracle home name.

Browse: Navigate the file system to find source and destination locations.

Table 1

(Cont.) Steps for Applying Oracle Application Server Patch

Screen

Action

3. Select a Product to Install

Select the following option:

Oracle Application Server Software Update

Select this option if you want to update your Oracle Application Server software and/or Oracle Developer Suite. You can update your Oracle Application Server middle-tier, or infrastructure.

The Software Update also updates the database schemas for Identity Management components.

For Middle-tier installations, this option may also upload data specific to the Middle-tier installation you are updating to the OracleAS Metadata Repository.

Click Next.

4. Instance Password

(Oracle Application

Server only)

Enter the ias_admin user password. This is the same password as the same as the Application Server Control password.

The Oracle Application Server or Identity Management instance that is receiving the update is displayed.

Click Next.

Table 1

(Cont.) Steps for Applying Oracle Application Server Patch

Screen

Action

5. Oracle Internet

Directory Login

Note: This screen only appears when patching the middle tier and Infrastructure that are associated with Oracle Internet Directory.

The update installation must connect to your Oracle Internet Directory.

The username and password identities you enter are determined by your enterprise consisting of either a single, or more than one Oracle Application Server realm.

You will see one of the following screens:

Single Realm: Oracle Internet Directory is configured for single realm.

You can connect either by:

Entering the username and password to login to the Oracle Internet Directory at the hostname and port of your Oracle Application Server installation.

You must be the Oracle Internet Directory superuser. Use cn=orcladmin as the username if you are the Oracle Internet Directory superuser.

Use your OracleAS Single Sign-On username if you have restricted installation privileges.

Multiple Realm: Oracle Internet Directory is configured for more than one realm.

You can connect either by:

Entering the username, password, and Identity Management Realm to connect and login to the Oracle Internet Directory at the hostname and port.

The Identity Management Realm is an area in Oracle Internet Directory where you administer user identities and groups.You must be the Oracle Internet Directory superuser to apply the update to Identity Management Realm. Use cn=orcladmin as the username if you are the Oracle Internet Directory superuser.

Use your OracleAS Single Sign-On username if you have restricted installation privileges.

6. OracleAS Certificate Authority Administrator

(Required only if OracleAS Certificate Authority is configured).

Enter the password for the OracleAS Certificate Authority Administrator. Updates to the Certificate Authority configured require administrative privileges.

Table 1

(Cont.) Steps for Applying Oracle Application Server Patch

Screen

Action

7. Enter Metadata

Repository SYS

Password

(Required only if selected update requires DBA access.)

Enter the password for the Metadata Repository SYS user on the selected database.

Shut down Identity Management clients. This includes:

Middle tiers using the Identity Management instance for authentication or identity services.

Distributed Identity Management installations or other Identity Management nodes which depend on this Identity Management instance for authentication or identity services.

Clustered Identity Management installations or other un-patched Identity Management instances which are a part of the Identity Management cluster.

8. Warning

Stop all the middle tier processes and clients of the Identity Management instance you are updating when prompted to do so.

All the processes of the selected Oracle home will be stopped at this point.

9. Summary

Verify your selections and click Install.

Oracle Process Manager and Notification Server (OPMN) and Oracle Enterprise Manager 10g processes will be stopped automatically.

10. Install Progress

This screen shows the progress of the Software Update.

11. Configuration

Assistants

This screen shows the progress of the configuration assistants. Configuration assistants perform updates to already configured components.

12. End of Installation

Click Exit to quit the installer.

7.1.4 Apply the Metadata Repository Update

The following procedure describes how to apply the OracleAS Metadata Repository Update.

1. Back up the Metadata Repository database before applying the Metadata Repository Update, if you have not already done so.

2. Perform the Software Update as detailed in Section 7.1.3, "Apply the OracleAS 10g Release 2 Patch Set 2 Software Update" prior to installing the Metadata Repository Update portion of OracleAS 10g Release 2 Patch Set 2.

Each middle tier installation that uses the Metadata Repository must have the Software Update prior to performing the Metadata Repository Update.

You can identify which middle tier installations are using a Metadata Repository by running the following command from either Identity Management or middle-tier installation. Oracle Internet Directory must be up and running before running the command.

In the preceding commands, the following variables were used:

OID Host: Oracle Internet Directory Server host name

OID SSL Port: Oracle Internet Directory Server Secure Sockets Layer (SSL) port

OID User: Distinguished name of an Oracle Internet Directory user (default is cn=orcladmin)

OID password: User password

GlobalDBName: Global Database Name for the Metadata Repository

3. Before running the Metadata Repository Update you must stop all Oracle Application Server middle-tier instances that use the Metadata Repository.

To stop your middle tier instances, use the following commands:

To stop the Application Server Control Console:

ORACLE_HOME/bin/emctl stop iasconsole

To stop your Oracle Application Server components:

ORACLE_HOME/opmn/bin/opmnctl stopall

This command stops OPMN and all OPMN-managed processes such as Oracle HTTP Server, OC4J instances, and OracleAS Web Cache.

4. Oracle Universal Installer is used to install the OracleAS 10g Release 2 Patch Set 2 Metadata Repository Update. Start the Oracle Universal Installer that came with the OracleAS 10g Release 2 Patch Set 2, as follows:

> ./runInstaller

5. Table 2 describes the steps and screens you will encounter during update of an OracleAS Metadata Repository.

Table 2

Steps for Applying Metadata Repository Update

Screen

Action

1. Welcome

Refer to Table 1 for the complete list of screen options.

2. Specify File

Locations

Refer to Table 1 for the complete list of screen options.

During the update you must specify one of the following Oracle home locations:

Portal and Wireless Middle Tier

Business Intelligence Middle Tier

Infrastructure containing both Identity Management and Metadata Repository

J2EE and Web Services Middle Tier (Standard Edition One only)

Portal Middle Tier (Standard Edition One only)

In OracleAS Portal only installation, Wireless will also be listed, but will not have an effect on the Metadata Repository update.

Table 2

(Cont.) Steps for Applying Metadata Repository Update

Screen

Action

3. Select a Product to Install

Select the following option:

Oracle Application Server Metadata Repository Update

Select this option to update the metadata stored in your OracleAS Metadata Repository that is used by your Oracle Application Server middle tiers.

You must run the Oracle Application Server Software Update on all of your Oracle Application Server middle-tier installations before using the Oracle Application Server Metadata Repository Update.

Click Next.

4. Applying Metadata

Repository Update

Select one of the following options:

Immediately install the update.

This option updates one of the registered Metadata Repositories during this installation session.

Save update files for later use.

This option copies the update files to the Oracle home, but does not apply them. The saved files can be used to manually update the OracleAS Portal repository and OracleAS Wireless repository at a later time. Refer to Section 7.1.6, "Update OracleAS Portal Repository Manually" for instructions on how to use the saved files for updating the OracleAS Portal repository or the OracleAS Wireless repository.

5. Application Server

Instance Password

Enter the password for the Oracle Application Server instance containing the OracleAS Metadata Repository that you are updating.

This is the same password for the ias_admin user and the same as the Application Server Control password.

Click Next.

6. Oracle Internet

Directory Login

Refer to Table 1 for the complete list of screen options.

7. Select OracleAS Metadata Repository

Select an available OracleAS Metadata Repository to update.

The software on all of your Oracle Application Server middle tier installations must be updated using the procedure described in Section 7.1.3, "Apply the OracleAS 10g Release 2 Patch Set 2 Software Update".

8. Enter Metadata

Repository SYS

Password

Enter the password for the Metadata Repository SYS user on the selected database.

Shut down any Metadata Repository clients that you are updating. This includes all Oracle Application Server middle tiers which are associated with the Metadata Repository.

9. Select Schema for Update

Select the Oracle Application Server products whose schema will be updated in the Metadata Repository. The existing schema must be at 10.1.2.x.x to be updated by this installation. Oracle Application Server products which are not listed do not have schema changes in this update release.

Table 2

(Cont.) Steps for Applying Metadata Repository Update

 

Screen

Action

10.

Warning

Stop all the middle tier processes and clients of the IM instance when asked to do so.

11.

Summary

Verify your selections and click Install.

12.

Install Progress

This screen shows the progress of patch set installation.

 

Note: Application of the OracleAS 10g Release 2 Patch Set 2 to an instance of Oracle Application Server that uses Oracle Internet Directory may take longer than expected. This may occur if there is a large amount of data in the Oracle Internet Directory.

13.

Configuration

This screen shows the progress of the configuration assistants. Configuration assistants update a single component schema.

Assistants

14.

End of Installation

Click Exit to quit the installer.

6.

Start the Oracle Application Server components, as follows:

 

ORACLE_HOME/opmn/bin/opmnctl startall

This command starts OPMN and all OPMN-managed processes such as Oracle HTTP Server, OC4J instances, and OracleAS Web Cache.

7.

Start the Application Server Control Console:

ORACLE_HOME/bin/emctl start iasconsole

7.1.5 Update OracleAS Portal Repositories that Reside in Oracle RAC Manually

If you are manually updating an OracleAS Portal repository (Section 7.1.6) that resides in a Oracle Real Application Clusters (Oracle RAC), then perform the following steps:

1. Create a TNS alias in the tnsnames.ora file for one of the active database instances in your cluster. The file is located in the following directory:

The current ORACLE_HOME/network/admin directory.

2. If it is applicable, turn off server-side load balancing in your Oracle RAC.

3. Follow the instructions described in Section 7.1.6, "Update OracleAS Portal Repository Manually" using the newly created TNS alias as the connect string.

4. If it is applicable, turn on the server-side load balancing in your Oracle RAC.

7.1.6 Update OracleAS Portal Repository Manually

This section describes the procedures for manual update of the OracleAS Portal Repository. You can apply this update to multiple repositories without repeated installation of the update to the same Oracle home. You can also use this update for an OracleAS Portal Repository that resides outside of the OracleAS Metadata Repository.

Note:

If your OracleAS Portal instance was originally installed

in release 3.0.9 or earlier, or if it was installed using ptlasst, then it resides outside of an OracleAS Metadata Repository and needs to be updated manually.

Perform the following steps to manually update your OracleAS Portal repository:

1. Apply the Software Update as detailed in Section 7.1.3, "Apply the OracleAS 10g Release 2 Patch Set 2 Software Update" to all middle-tier Oracle homes that are associated with your OracleAS Portal repository if it has not already been done.

The OracleAS Portal instance will not function properly if the repository is updated before the middle tiers that are configured for that repository.

2. Create a cold backup of the database in which your OracleAS Portal repository resides.

3. Apply the Metadata Repository Update as detailed in Section 7.1.4, "Apply the Metadata Repository Update".

The update can be performed using either available installation option:

Save update files for later use.

When choosing this option, the OracleAS Portal repository is not updated and the files needed to perform the update are simply copied to your Oracle home. This option is useful when there are no OracleAS Portal repositories residing in an OracleAS Metadata Repository that need updating, or when all instances will be updated manually. The update can be performed from any OracleAS middle-tier Oracle home or from an infrastructure Oracle home that contains both a Metadata Repository and an Oracle Identity Management installation.

Immediately install the update.

When choosing this option, the files needed to perform the update are copied over to your Oracle home and then the OracleAS Portal repository in the selected Metadata Repository is updated. This option can be chosen, for example, to update an OracleAS Portal repository residing in a Metadata Repository before running the update manually on an OracleAS Portal instance residing outside of a Metadata Repository. This mode also copies the files over that are necessary to perform any subsequent updates to other repositories, so you can then use the installed files to manually update any remaining OracleAS Portal instances that you use. The update can be performed from any middle-tier Oracle home that is associated with the Metadata Repository being updated, or from the infrastructure Oracle home that contains the installation of the Metadata Repository being updated. After the installation, the files that are copied over can be used to manually update any other Portal repositories.

A manual update on the repository that was updated

automatically when this option was chosen should not be attempted. The update will fail because it has already occurred.

Note:

4.

Set your ORACLE HOME environment variable to the Oracle home where the Metadata Repository Update was applied.

5. Obtain the OracleAS Portal Schema Password.

If your OracleAS Portal schema resides in the OracleAS Metadata Repository, then the password will be randomized. Use the Oracle Directory Manager to obtain the password.

a. Start Oracle Directory Manager as follows:

Use the following command:

ORACLE_HOME/bin/oidadmin

b. Log in to Oracle Directory Manager as the orcladmin user.

c. Expand Entry Management in the System Objects section. Enter the following values:

cn=OracleContext

cn=Products

cn=IAS

cn=IAS Infrastructure Databases

OrclReferenceName=Infrastructure database name for OracleAS Metadata Repository, such as asdb.server.domain.com

d. Select the OrclResourceName=PORTAL entry to view the Portal schema password.

e. Click the Properties tab to view the schema password in the orclpasswordattribute field.

6. Verify you can connect to the OracleAS Portal schema through SQL*Plus using the schema password and the TNS name from the Oracle home where the Metadata Repository Update was applied.

For example:

sqlplus portal/ACOxlc22@asdb

7. Stop all Oracle Application Server services in the middle-tier Oracle homes that are associated with the OracleAS Portal repository being updated as follows:

To stop the Application Server Control Console:

ORACLE_HOME/bin/emctl stop iasconsole

To stop Oracle Application Server components:

ORACLE_HOME/opmn/bin/opmnctl stopall

This command stops OPMN and all OPMN-managed processes such as Oracle HTTP Server, OC4J instances, and OracleAS Web Cache.

8. Verify the Oracle Internet Directory associated with the OracleAS Portal schema is up and running.

9. Go to the following directory in the Oracle home where the Metadata Repository Update was applied.

portal/upg/plsql

The directory was created during the Metadata Repository update. If the directory does not exist in your Oracle home, then either the update has not been applied or the update was applied to a different Oracle home.

10. Run the upgrade script in precheck mode until there are no errors in the log. The script generates the upgrade.log file and the upgrade directory, tmp, in the current directory. The syntax is as follows:

ORACLE_HOME/portal/upg/plsql/patch.sh -precheck

When the -precheck option is specified, only the pre-upgrade checks are done and the upgrade exits afterward. In this mode, the upgrade is not immediately terminated if a precheck fails. Instead, the errors for all prechecks are consolidated in the upgrade.log file. Look at the end of the log to see a list of checks that failed. Run the script in this mode until the precheck does not fail. In this mode, the schema is not altered, so restoring from your backup is not necessary between runs.

11. Run the upgrade script without parameters after resolving all warnings and errors from the precheck step. The syntax is as follows:

ORACLE_HOME/portal/upg/plsql/patch.sh

The script prompts you for information about the system setup. Your answers are echoed back for verification at the end of the script.

Table 3 shows the questions from the script. Default answers to the questions are given in brackets.

Table 3

Upgrade Script Prompts

Prompt

Explanation

Have you backed up your database (y|n)? [y]:

If you have backed up the database, then answer y.

If you have not backed up the database, then answer n, back up the database and restart the script.

Enter the name of the schema you would like to upgrade [portal]:

If your schema name is different from the default OracleAS Infrastructure installation schema name of portal, then enter the schema name.

Enter the password of the schema you would like to upgrade [portal]:

Enter the database password for the schema that is to be updated.

Enter the password for the SYS user of your database [change_ on_install]:

Enter the password for the SYS user.

Enter the TNS connect string to connect to the database [orcl]:

Provide the TNS connect string (found in the ORACLE_ HOME/network/admin/tnsnames.ora file).

Table 3

(Cont.) Upgrade Script Prompts

Prompt

Explanation

At this point, no changes have been made to the database. Please review all the details displayed above. If you choose to stop the upgrade at this point, you will be able to start it again without restoring from a backup. If you continue and a problem occurs, you will have to retrieve your backup and start over. Is this information correct (y/n)? [y]:

Verify that the answers are correct, and answer the question:

Enter y to proceed with the upgrade.

Enter n to stop the upgrade. If necessary, you can run the upgrade script again, correcting answers as needed.

If you have entered any incorrect information, then answer n. This will allow you to exit before any changes are made by the script.

12. Examine the upgrade.log file.

Any errors that occurred during the upgrade are captured in the upgrade.log file. You should examine this file to ensure that there were no errors and that the upgrade was successful.

a. Locate the upgrade.log log file. The location is the current directory.

b. Open the log with a text editor.

c. Go to the end of the file. You will either see a success message or a set of errors.

d. Check Oracle Application Server Portal Error Messages Guide for any errors or warnings. The guide is available at Oracle Technology Network at

http://www.oracle.com/technology

Most errors require that you restore the repository, fix the problem, and re-run the upgrade. Contact Oracle Support if there are any errors not shown in the guide.

You cannot run OracleAS Portal until there is a successful upgrade. A successful upgrade has no errors.

The following is an example of the end of the log file after a successful upgrade. It includes the "Upgrade completed successfully" message and does not have any error messages:

Example 1 Log File after Successful Upgrade

### Show errors and warnings Step started at Tue Jul 12 04:17:22 2005 ### ### WARNING: WWU-26002: Upgrade completed with the following warnings:

.

### Upgrade completed successfully

.

Upgrade Ended at Tue Jul 12 04:17:31 2005

The following examples show the log files from unsuccessful upgrades. Notice the line numbers preceding the errors in Example 3.

Example 2 Premature Termination Showing Error Section

### ERROR: WWU-01013: Upgrade terminated with the following errors:

###

1278 : EXP-00003: no storage definition found for segment

###

(9, 10251) 1368 : ### ERROR: Exception Executing Script

.

upg/common/precln/

/frwk/export.pl /

:

### Upgrade aborted at Thu Jun 30 04:28:18 2005.

Example 3 Standard Termination, but with Errors

### ### Show errors and warnings ### Upgrade step started at Fri Jul 1 03:52:56 2005 ###

### WARNING: WWU-26002: Upgrade completed with the following warnings:

### ### ### ERROR: WWU-01012: Upgrade completed with the following errors:

###

8503:ERROR at line 1:

###

8504 : ORA-20000:

###

8505 : ORA-06512: at "UPGR309.WWPOF", line 440

. . Upgrade Ended at Fri Jul 1 04:28:08 2005

.

13. Start all Oracle Application Server services in the middle-tier Oracle homes that are associated with the OracleAS Portal repository that was just updated as follows:

To start Oracle Application Server components:

ORACLE_HOME/opmn/bin/opmnctl startall

To start the Application Server Control Console:

ORACLE_HOME/bin/emctl start iasconsole

14. Test your updated OracleAS Portal instance.

7.1.7 Update OracleAS Wireless Repository Manually

This section describes the procedures for a manual update of the OracleAS Wireless Repository.

1. Apply the Software Update as detailed in Section 7.1.3, "Apply the OracleAS 10g Release 2 Patch Set 2 Software Update" to all middle-tier Oracle homes that are associated with your OracleAS Wireless repository, if it has not already been done.

2. Apply the Metadata Repository Update as detailed in Section 7.1.4, "Apply the Metadata Repository Update".

The update can be performed using either available installation option:

Save update files for later use.

When choosing this option, the OracleAS Wireless repository is not updated and the files needed to perform the update are simply copied to your Oracle home. This option is useful when there are no OracleAS Wireless repositories residing in an OracleAS Metadata Repository that need updating, or when all instances will be updated manually. The update can be performed from any OracleAS middle-tier Oracle home or from an infrastructure Oracle home that contains both a Metadata Repository and an Oracle Identity Management installation.

Immediately install the update.

When choosing this option, the files needed to perform the update are copied over to your Oracle home and then the OracleAS Wireless repository in the selected Metadata Repository is updated. This option can be chosen, for example, to update an OracleAS Wireless repository residing in a Metadata Repository before running the update manually on an OracleAS Wireless instance residing outside of a Metadata Repository. This mode also copies the files over that are necessary to perform any subsequent updates to other repositories, so you can then use the installed files to manually update any remaining OracleAS Portal instances that you use. The update can be performed from any middle-tier Oracle home that is associated with the Metadata Repository being updated, or from the infrastructure Oracle home that contains the installation of the Metadata Repository being updated. After the installation, the files that are copied over can be used to manually update any other Wireless repositories.

A manual update on the repository that was updated

automatically when this option was chosen should not be attempted. The update will fail because it has already occurred.

Note:

3. Use the following command to apply the OracleAS Wireless update. The ORACLE_HOME environment variable must be set for the script to run.

For Solaris:

$ORACLE_HOME/wireless/upgrade_infra/bin/patchinfra.sh -P password -C tnsname

For example:

$ORACLE_HOME/wireless/upgrade_infra/install/patchinfra.sh -P YXYhR16V -C "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)

(HOST=rhine985.us.myco.com)(PORT=1521)))

(CONNECT_DATA=(SERVICE_NAME = asdb.us.myco.com)))"

For Windows:

ORACLE_HOME\wireless\upgrade_infra\bin\patchinfra.bat -P password -C tnsname

For example:

ORACLE_HOME\wireless\upgrade_infra\install\patchinfra.bat -P YXYhR16V -C "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)

(HOST=rhine985.us.myco.com)(PORT=1521)))

(CONNECT_DATA=(SERVICE_NAME = asdb.us.myco.com)))"

In the preceding commands, password is the OracleAS Wireless schema password, and tnsname is the net description string.

Note:

The password is passed in clear text. To have an encoded

password, use the - E option with the encoded password instead of the -P option.

7.2 Applying OracleAS 10g Release 2 Patch Set 2 on OracleAS Cluster

(Identity Management) Environments

This section describes how to apply OracleAS 10g Release 2 Patch Set 2 to an OracleAS Cluster (Identity Management) environment. Before applying the patch set, consider the following:

Oracle Internet Directory may be the only Identity Management component in its Oracle home or it can be co-located with other Identity Management components. If it is co-located, then shutting down Oracle Internet Directory indicates that you will need to shut down all Identity Management components, and starting Oracle Internet Directory indicates starting all Identity Management components.

LDAP traffic can be directed to a node as soon as it has been patched to 10g Release 2 (10.1.2.2.0). It is not necessary to patch all Oracle Internet Directory nodes before directing traffic.

- If there is an LDAP load balancer in the environment, then ensure that the load balancer routes LDAP traffic to the patched Oracle Internet Directory nodes only.

The following steps describe how to apply OracleAS 10g Release 2 Patch Set 2 to OracleAS Cluster (Identity Management) environments.

1. Do a full backup of the OracleAS Metadata Repository and the individual Identity Management Oracle homes.

Note:

If patch application fails for any reason, then a complete

restoration of the OracleAS Metadata Repository and Oracle Identity Management Oracle homes will be required prior to retrying patch application.

2. Select one Identity Management node for installation of the patch set, such as

IM_Node1.

3. Ensure that the Identity Management instance is up and running on the node.

4. Use the following command on all other Identity Management nodes so that only the first node, IM_Node1, remains in the cluster:

dcmctl leavecluster

5. Shut down the Identity Management instances on all other Identity Management nodes. If the instances are not shut down, then the installer will give the following error while patching IM_Node1:

Oracle Universal Installer has detected active Oracle Internet Directory

instances connected to the OracleAS Metadata Repository. All Oracle Identity Directory instances using the OracleAS Metadata Repository must be shut down before continuing.

6. Apply OracleAS 10g Release 2 Patch Set 2 on the first node, IM_Node1,

according to the instructions in Section 7.1, "Applying OracleAS 10g Release

2 Patch Set 2".

The Identity Management instance will be up and running after applying the patch. Leave it up and running.

7. Select another Identity Management node, IM_Node2.

8. Start Identity Management on this node, IM_Node2.

9. Apply OracleAS 10g Release 2 Patch Set 2 to the second node, IM_Node2,

according to the instructions in Section 7.1, "Applying OracleAS 10g Release

2 Patch Set 2".

The Identity Management instance will be up and running after applying the patch. Leave it up and running.

10. Use the following command to join IM_Node2 to the DCM cluster:

dcmctl joincluster -cl cluster

In the preceding command, cluster is the name of the cluster.

11. Use the following command to bring up the Oracle Application Server Single Sign-On/Oracle Delegated Administration Services applications:

opmnctl startall

12. Repeat steps 7 through 11 for each subsequent Identity Management node in the cluster, one node at a time.

7.3 Installing OracleAS 10 g Release 2 Patch Set 2 on Distributed

OracleAS Cluster (Identity Management) Environments

The following steps describe how to apply OracleAS 10g Release 2 Patch Set 2 to a distributed OracleAS Cluster (Identity Management) environments. Before applying the patch set, note the following:

Oracle Internet Directory may be the only Identity Management component in its Oracle home or it can be co-located with other Identity Management components. If it is co-located, then shutting down Oracle Internet Directory requires that you will need to shut down all Identity Management components, and starting Oracle Internet Directory requires starting all Identity Management components.

LDAP traffic can be directed to a node as soon as it has been patched to 10g Release 2 (10.1.2.2.0). It is not necessary to patch all Oracle Internet Directory nodes before directing traffic.

- In a distributed Identity Management configuration, the Oracle Application Server Single Sign-On/Oracle Delegated Administration Services Oracle patching can start as soon as one Oracle Internet Directory node is patched to 10g Release 2 (10.1.2.2.0). This will minimize overall downtime.

- If there is an LDAP load balancer in the environment, then ensure that the load balancer routes LDAP traffic to the patched Oracle Internet Directory nodes only.

1. Do a full backup of the OracleAS Metadata Repository, the individual Oracle Internet Directory Oracle homes, and the individual Oracle Application Server Single Sign-On/Oracle Delegated Administration Services Oracle homes.

Note:

If patch application fails for any reason, then a complete

restoration of the OracleAS Metadata Repository and Oracle Identity Management Oracle homes will be required prior to retrying patch application.

2. Select one Oracle Application Server Single Sign-On/Oracle Delegated Administration Services node for installation of the patch set, such as SSO_

Node1.

3. Use the following command on all other Oracle Application Server Single Sign-On/Oracle Delegated Administration Services nodes so that only the first node, SSO_Node1, remains in the cluster:

dcmctl leavecluster

4. Shut down all Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instances running against the Oracle Internet Directory environment that you will be applying the patch, including SSO_

Node1.

5. Select one Oracle Internet Directory node, OID_Node1, and ensure Oracle Internet Directory is up and running on the node.

6. Shut down Oracle Internet Directory on all other Oracle Internet Directory nodes. If Oracle Internet Directory on the other nodes is not shut down, then the installer will give the following error while patching OID_Node1.

Oracle Universal Installer has detected active Oracle Internet Directory instances connected to the OracleAS Metadata Repository. All Oracle Identity Directory instances using the OracleAS Metadata Repository must be shut down before continuing.

7. Apply OracleAS 10g Release 2 Patch Set 2 on the Oracle Internet Directory node, OID_Node1, according to the instructions in Section 7.1, "Applying OracleAS 10g Release 2 Patch Set 2".

The Oracle Internet Directory instance will be up and running after applying the patch. Leave it up and running.

8. Ensure the LDAP load balancer in the configuration routes LDAP traffic to the patched Oracle Internet Directory node, OID_Node1, only.

9. In order to minimize downtime, the first Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instance can be patched. The following steps describe how to patch the Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instance.

If you prefer to patch all the Oracle Internet Directory instances prior to the patching Oracle Application Server Single Sign-On/Oracle Delegated Administration Servicesinstance, then go to step 10.

a. Start the first Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instance, SSO_Node1.

b. Apply OracleAS 10g Release 2 Patch Set 2 to SSO_Node1, according to the instructions in Section 7.1, "Applying OracleAS 10g Release 2 Patch Set 2". The Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instance will be up and running after applying the patch. Leave it up and running.

c. Select another Oracle Application Server Single Sign-On/Oracle Delegated Administration Services node, SSO_Node2.

d. Start OracleAS Single Sign-On on the second node.

e. Apply OracleAS 10g Release 2 Patch Set 2 to the second node, SSO_ Node2, according to the instructions in Section 7.1, "Applying OracleAS 10g Release 2 Patch Set 2". The Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instance will be up and running after applying the patch. Leave it up and running.

f. Use the following command to join SSO_Node2 to the DCM cluster:

dcmctl joincluster -cl cluster

In the preceding command, cluster is the name of the cluster.

g. Use the following command to bring up the Oracle Application Server Single Sign-On/Oracle Delegated Administration Services applications:

opmnctl startall

h. Repeat steps c through g for each subsequent Oracle Application Server Single Sign-On/Oracle Delegated Administration Services node, one at a time.

i. Select another Oracle Internet Directory node, OID_Node2.

j. Start the Oracle Internet Directory instance on the second Oracle Internet Directory node, OIDNode2.

k. Apply OracleAS 10g Release 2 Patch Set 2 to the second Oracle Internet Directory node, OID_Node2, according to the instructions in Section 7.1, "Applying OracleAS 10g Release 2 Patch Set 2".

The Oracle Internet Directory instance will be up and running after applying the patch Leave it up and running.

l. Repeat steps i through k for each subsequent Oracle Internet Directory node, one at a time.

m. Reconfigure the LDAP load balancer in the environment to route LDAP traffic to all patched Oracle Internet Directory nodes.

10. Use the following steps to apply the patch set to all remaining Oracle Internet Directory instances before the Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instances.

If you prefer to apply the patch to one Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instance in order to minimize downtime, the follow the steps in step 9.

a. Select a second Oracle Internet Directory node, OID_Node2.

b. Start the Oracle Internet Directory instance on this node.

c. Apply OracleAS 10g Release 2 Patch Set 2 to the second node, OID_ Node2. The Oracle Internet Directory instance will be up and running after applying the patch. Leave it up and running.

d. Repeat steps b and c for each subsequent Oracle Internet Directory node, one at a time.

e. Start the Oracle Application Server Single Sign-On/Oracle Delegated Administration Services instance on the first Oracle Application Server Single Sign-On/Oracle Delegated Administration Services node, SSO_ Node1. This node was selected in step 2.

f. Apply OracleAS 10g Release 2 Patch Set 2 to the node. The Oracle Application Server Single Sign-On instance will be up and running at the end of the installation. Leave it up and running.

g. Select another Oracle Application Server Single Sign-On/Oracle Delegated Administration Services node, SSO_Node2.

h. Start Oracle Application Server Single Sign-On on the second node, SSO_

Node2.

i. Apply OracleAS 10g Release 2 Patch Set 2 to the node. The Oracle Application Server Single Sign-On instance will be up and running after applying the patch. Leave it up and running.

j. Use the following command to join SSO_Node2 to the DCM cluster:

dcmctl joincluster -cl cluster

In the preceding command, cluster is the name of the cluster.

k. Use the following command to bring up the Oracle Application Server Single Sign-On/Oracle Delegated Administration Services applications:

opmnctl startall

l. Repeat steps g through k for each subsequent Oracle Application Server Single Sign-On/Oracle Delegated Administration Services node, one at a time.

m. Reconfigure the LDAP load balancer in the configuration to route LDAP traffic to all the patched Oracle Internet Directory nodes.

7.4 Applying OracleAS 10 g Release 2 Patch Set 2 on OracleAS Portal

10.1.4 to Upgrade to OracleAS Portal 10.1.4.1

If your OracleAS Portal repository is version 10.1.4, you must first apply OracleAS 10g Release 2 Patch Set 2 against the middle tier and Infrastructure. This patches the middle tier and Infrastructure to version 10.1.2.2. Then, apply the 10.1.2.2 Metadata Repository update against OracleAS Portal repository 10.1.4 to upgrade it to 10.1.4.1.

If you have upgraded the OracleAS Portal repository to 10.1.2.2 from 10.1.2.x and later you want to upgrade to OracleAS Portal 10.1.4.1, you must do the following:

1. Upgrade the OracleAS Portal repository to 10.1.4.

2. Re-apply the 10.1.2.2 Metadata Repository update against OracleAS Portal repository 10.1.4 to upgrade it to 10.1.4.1.

Follow the instructions in Section 7.1.4, "Apply the Metadata Repository Update" to apply the OracleAS Portal 10.1.4.1.0 patch.

If you are manually upgrading OracleAS Portal in a customer database, refer to the instructions in Section 7.1.6, "Update OracleAS Portal Repository Manually".

7.5 Applying OracleAS 10 g Release 2 Patch Set 2 on Oracle Developer

Suite

Table 4 describes how to apply OracleAS 10g Release 2 Patch Set 2 against an Oracle Developer Suite 10.1.2.0.2 installation.

Table 4

Developer Suite

Steps for Applying Oracle Application Server Patch Against Oracle

 

Screen

Action

1.

Welcome

The Welcome screen provides information about Oracle Universal Installer.

The following buttons appear on the installation screens:

Deinstall Products: Deinstall individual components or the entire product. This button appears only on the Welcome screen.

About Oracle Universal Installer: View the version number of the installer.

Help: Access detailed information about the functionality of each screen.

Installed Products: View currently installed products or deinstall the entire product or components.

Back: Return to the previous screen. This button is disabled on the Welcome screen.

Next: Proceed to the next screen.

Install: Install the selected product. This button is disabled on the Welcome screen.

Cancel: Quit the installation process and exit the installer.

Click Next to continue.

Table 4

(Cont.) Steps for Applying Oracle Application Server Patch Against Oracle

Developer Suite

Screen

Action

2. Specify File

Locations

Check the default source path, destination name, and destination path shown on the Specify File Location page for your update of your installed Oracle Developer Suite software. If you do not want to use the defaults, then enter the values you want to use.

The Specify File Locations screen allows you to enter the full path for the source and destination locations for your update of Oracle Developer Suite software. The Name and Path fields must have the same values as the base installation.

Source: This is the full path to the products.xml file from which the product will be installed. The installer detects and uses the default values of the products.xml file of the installation program. Do not change the path.

Name: Select the Oracle home name for the environment to be patched.

Oracle homes are identified by name. The Oracle home name identifies the program group associated with a specific Oracle home and the installed Oracle services associated with the home.

Path: This is the full path to the Oracle home for application of the Software Update.

This field is filled automatically when you select the Oracle home name.

Browse: Navigate the file system to find source and destination locations.

Click Next to continue.

3. Select a Product to Install

Select the following option:

Oracle Application Server Software Update

Select this option if you want to update your Oracle Application Server software and/or Oracle Developer Suite.

Click Next to continue.

4. Summary

Verify your selections and click Install.

5. Install Progress

This screen shows the progress of the Software Update.

6. End of Installation

Click Exit to quit the installer.

7.6 Silent and Non-Interactive Patch Application

This section describes how to apply OracleAS 10g Release 2 Patch Set 2 either by silent or non-interactive methods. Use silent patch application when you want to do similar applications to more than one computer. You can also use silent patch application to apply from a remote location using the command line. Use non-interactive patch application when you want to see specific screens, or when you want to enter some information interactively.

To do a silent or non-interactive patch application, you supply the installer with a text file called a response file. The installer uses the variables and parameter

values in the response file to provide answers to some or all of the installer prompts.

7.6.1 Silent Installation

With silent installation, you do not need to monitor the installation because you do not enter information, and you do not have a graphical user interface to watch.

To do a silent installation, supply the installer with a response file and specify the -silent flag on the command line.

7.6.2 Non-interactive Installation

With non-interactive installation, the installer displays a graphical user interface as in a normal installation. If your response file does not have an entry for a particular installer prompt, then you must provide the response during the installation.

7.6.3 Response Files

You must create a response file before you install the patch set. You can edit the response files with any text editor. Start by copying the response file templates oracle.iappserver.patchset.rsp (Software Update) and oracle.iappserver.dbpatch.rsp (Metadata Repository Update) provided in the following directory of your OracleAS 10g Release 2 Patch Set 2 product installation media:

stage/Response

In the template, parameters have three types of values:

Constants

Optional Values

Required Values

The following sections describe the parameters.

Constants

These are text or Boolean values that are pre-set to give you a successful patch set application. Unless you are an advanced user, do not change these values.

Examples:

FROM_LOCATION=" /stage/products.xml" SHOW_SUMMARY_PAGE=false

Optional Values

When a parameter is set to the string <Value Unspecified>, the installer ignores the parameter. The installer either uses the default value for the parameter, or obtains the value from your current Oracle Application Server 10g Release 2 (10.1.2) installation. Unless you are an advanced user, do not change these values.

Examples:

UNIX_GROUP_NAME=<Value Unspecified>

Required Values

When a parameter is set to the string <Value_Required>, you must replace the string with a text or Boolean value. For a silent patch application, if you do not supply a value, then the process will fail. For a non-interactive patch application, if you do not replace the string with a text or Boolean value, then the process will pause and display the normal screen that prompts for this value.

The OracleAS 10g Release 2 Patch Set 2 application requires values for the following parameters:

- ORACLE_HOME

This is the full path of the Oracle home directory that contains the Oracle Application Server installation you want to patch.

* For a silent patch application, you must update the entry

ORACLE_HOME=<Value_Required>

with the path to your Oracle home, as follows:

ORACLE_HOME="/private/oracle/AppSrvHome"

If you do not update the entry, then the process will fail.

* For a non-interactive patch application, if you do not update the entry, then the installer will pause and display the File Locations dialog.

- szl_InstanceInformation

This is the instance password for the current Oracle Application Server 10g instance. The password value must match the existing password already established for the instance. The password must be specified in clear text. For security reasons, restrict access to the silent application response files and delete them when they are no longer needed. The following describe how to use the parameter:

* For software update application on middle tiers associated with OracleAS Portal, OracleAS Wireless, or J2EE installations associated with Oracle Internet Directory.

oracle.iappserver.st_midtier:szl_InstanceInformation=<Value

Unspecified>

oracle.iappserver.st_midtier:szlSpecifyOIDLogin=<Value

Unspecified>

* For J2EE installations not associated with Oracle Internet Directory

oracle.iappserver.st_midtier:szl_InstanceInformation=<Value

Unspecified>

* For Developer Kits installations

oracle.iappserver.devkit:szl_InstanceInformation=<Value

Unspecified>

* For infrastructure installations

oracle.iappserver.st_infrastructure:szl_InstanceInformation=<Value

Unspecified>

oracle.iappserver.st_infrastructure:szlSpecifyOIDLogin=<Value

Unspecified>

szl_SYSPassword=<Value Unspecified>

szl_OCAInformation=<Value Unspecified>

The szl_OACInformation parameter is required if Oracle Application Server Certificate Authority is configured for the environment.

7.6.4 Performing Silent or Non-interactive Patch Application

The following procedure describes how to perform silent or non-interactive patch application:

Note:

If any files are in use during a silent patch application, such as

a user has an open file, then the process may terminate. If that happens, then the open file must be determined and its corresponding process shut down. The patch application can be restarted after shutting down the process.

1. Copy the response file template from the product installation media to your computer.

2. Make the necessary changes to the copy of the file, and save it.

3. Start the patch application. Specify the response file path and filename as the value of the installer’s responseFile parameter. For a silent installation, also specify the silent parameter.

Examples:

Silent patch application:

> ./runInstaller -silent -responseFile absolute_path_and_filename

Non-interactive patch application

> ./runInstaller -responseFile absolute_path_and_filename

4. Check the log files in your inventory directory for any errors.The log files are located in the following directory:

/oracle_inventory_path/logs/installActiontodays_date_time.log

The value of oracle_inventory_path is stored in the following file:

/var/opt/oracle/oraInst.loc

The log file name has the format installActionstodays_date_ time.log.

7.7 Failure During Software Update

If there is a failure during application of the Software Update, then Oracle recommends restoring your Oracle Application Server installation from the backup version, and retrying application of the patch.

If you have no backup installation available and want to retry application of the Software Update after a failure, then try the following steps:

1. Correct the issue that caused the original failure during application of the Software Update.

2. Start the Software Update application.

3. When the Available Products screen is displayed, expand all of the tree elements on the screen and select all the checkboxes next to the individual patch names.

4. Continue the Software Update application.

8 Postapplication Considerations

This section describes postapplication considerations for OracleAS 10g Release 2 Patch Set 2. It contains the following topics:

Section 8.1, "Perform a Complete Backup"

Section 8.2, "Update File Permissions"

Section 8.3, "Re-application of the OracleAS 10g Release 2 Patch Set 2"

Section 8.4, "Restart OracleAS Metadata Repository Processes in Distributed Environment"

Section 8.5, "Configuration Assistant Log Files"

Section 8.6, "Directories and Files Backed up by Oracle Universal Installer"

Section 8.7, "Installing Patch 4700543 for OracleAS Web Cache"

Section 8.8, "OracleMetaLink Notes"

8.1 Perform a Complete Backup

It is necessary to perform a complete backup of your Oracle Application Server environment after installing the patch set. Earlier backups will not work with the updated Oracle Application Server Backup and Recovery Tool.

8.2 Update File Permissions

After applying OracleAS 10g Release 2 Patch Set 2, you need to update the file permissions for the ORACLE_HOME/sso/bin/ssoreg.sh file. The following is an example of the command:

chmod ug+x ORACLE_HOME/sso/bin/ssoreg.sh

8.3 Re-application of the OracleAS 10 g Release 2 Patch Set 2

During re-application of OracleAS 10g Release 2 Patch Set 2, the Available Product Components screen is displayed. To continue with patch application, you must expand the component tree and manually select all of the components for patch re-application. Failure to do so will prevent successful re-application of OracleAS 10g Release 2 Patch Set 2.

8.4

Restart OracleAS Metadata Repository Processes in Distributed

Environment

If you have a distributed environment with an Infrastructure with Oracle Internet Directory and OracleAS Metadata Repository on one computer, computer1, and an Infrastructure with OracleAS Metadata Repository on another computer, computer2, then you should restart the processes on the computer2 after applying the patch sets. The following steps describe how to restart the processes on computer2:

1. Start the Net Listener as follows:

ORACLE_HOME/bin/lsnrctl start

2. Start the OracleAS Metadata Repository instance as follows:

ORACLE_HOME/bin/sqlplus /nolog SQL> connect SYS as SYSDBA SQL> startup SQL> quit

8.5 Configuration Assistant Log Files

The locations for specific Oracle Application Server configuration assistant log files are described in the Oracle Application Server Installation Guide.

8.6 Directories and Files Backed up by Oracle Universal Installer

Table 5 lists the OracleAS Portal directories backed up by Oracle Universal Installer during installation of OracleAS 10g Release 2 Patch Set 2.

Table 5

OracleAS Portal Directories Backed up by Oracle Universal Installer

From

To

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/applications/jpdk/jpdk/

Portal.timestamp/applications/jpd

htdocs

k/jpdk/htdocs

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/applications/jpdk/jpdk/

Portal.timestamp/applications/jpd

WEB-INF

k/jpdk/WEB-INF

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/application_

Portal.timestamp/application_

deployments/jpdk

deployments/jpdk

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/applications/jpdk/pdkst

Portal.timestamp/applications/jpd

ruts/htdocs

k/pdkstruts/htdocs

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/applications/jpdk/pdkst

Portal.timestamp/applications/jpd

ruts/WEB_INF

k/pdkstruts/WEB_INF

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/applications/portalTool

Portal.timestamp/applications/por

s/providerBuilder/WEB-INF

talTools/providerBuilder/WEB-INF

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/applications/portalTool

Portal.timestamp/applications/por

s/omniPortlet/WEB-INF

talTools/omniPortlet/WEB-INF

Table 5

(Cont.) OracleAS Portal Directories Backed up by Oracle Universal

From

To

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/applications/portalTool

Portal.timestamp/applications/por

s/omniPortlet/plugins

talTools/omniPortlet/plugins

ORACLE_HOME/j2ee/OC4J_

ORACLE_HOME/j2ee/OC4J_

Portal/applications/portalTool

Portal.timestamp/applications/por

s/webClipping/WEB-INF

talTools/webClipping/WEB-INF

ORACLE_HOME/portal/conf

ORACLE_HOME/portal.timestamp/conf

Table 6 lists the OracleAS Portal files backed up by Oracle Universal Installer during installation of OracleAS 10g Release 2 Patch Set 2:

Table 6

OracleAS Portal Files Backed up by Oracle Universal Installer

From

To

ORACLE_

ORACLE_

HOME/portal/pdkjava/providerGr

HOME/portal.timestamp