Hi All,
It’s my pleasure to inform every one those who are following this blog iam not working on this or updating on regular intervals.
iam currently active on http://appsjagan.blogspot.com
May 24, 2014
November 23, 2009
APPS 11.5.10.2 Installation on OEL5
Oracle® Applications
| Doc ID: | 316806.1 |
Installation Update Notes
Release 11i (11.5.10.2) for Linux x86, Solaris SPARC, Microsoft Windows, HP-UX PA-RISC, HP-Tru64, IBM AIX
Revised: October 2009
This document updates Installing Oracle Applications and Upgrading Oracle Applications with platform-specific information for Oracle Applications Release 11i (11.5.10.2). Refer to the information contained here, and to the appropriate manual, when you install or upgrade your system.
This document may be updated on a weekly basis. Currently, it contains the following sections:
- General Requirements for All Operating Systems
- General Requirements for UNIX/Linux
- Linux x86 and Linux x86-64 (AMD64/EM64T) Requirements
- Solaris SPARC Requirements
- HP-UX PA-RISC Requirements
- HP-Tru64 Requirements
- IBM AIX Requirements
- General Requirements for Windows
- Windows Server 2003 Requirements
- Current Revisions Log
The latest version of this document, and the latest certified operating system requirements, are available on OracleMetaLink. The Oracle Applications Release Notes and Oracle Applications NLS Release Notes, also available on OracleMetaLink, describe additional required tasks, including applying AD patches and any Consolidated Update patches that apply to the products in your system.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
General Requirements for All Operating Systems
The notes in this section apply to Linux x86 and Linux x86-64 (AMD64/EM64T), Solaris SPARC, HP-UX PA-RISC, HP-Tru64, IBM AIX, and Windows x86 operating systems.
Start Here DVD
Be sure to download and apply the latest Rapid Install patch as described in the Oracle Applications Release Notes before you begin your installation or upgrade.
Operating System Versions
The operating system versions supported are listed in the following table. See Certify on OracleMetaLink for the latest information.
| Note:You can only install Oracle Applications on an x86-64 architecture server if the operating system is 32-bit Linux or Windows. If your operating system is 64-bit, contact your operating system vendor to obtain a 32-bit operating system before installing Oracle Applications. |
| Operating System Name | Supported Version |
| Oracle Enterprise Linux (32-bit) | 4, 5 – installation and maintenance pack |
| Red Hat Enterprise Linux AS/ES (32-bit) | 2.1¹, 3, 4, 5 – installation and maintenance pack |
| SUSE Linux Enterprise Server (32-bit) | 8, 9, 10 – installation and maintenance pack |
| Solaris SPARC | 6 (5.6)² – maintenance pack |
| 8 (5.8), 9 (5.9), 10 (5.10) – installation and maintenance pack | |
| HP-UX PA-RISC | 11.11, 11.23, 11.31 – installation and maintenance pack |
| HP-UX Itanium** | 11.23, 11.31 – installation |
| HP-Tru64 | 5.1A³, 5.1B – installation and maintenance pack |
| 4.0F³, 4.0G³ – maintenance pack | |
| IBM AIX | 5L (5.24, 5.3), 6 (6.1) – installation and maintenance pack Note: New Release 11.5.10.2 installations and maintenance upgrades to this release level are not supported on IBM AIX 4.3.3. See OracleMetaLink note 233657.1 for desupport information. |
| Windows x86 | Windows 2000 (all server editions) |
| Windows Server 2003 (all editions) | |
| Footnotes:¹In accordance with the Red Hat Enterprise Linux Errata Support Policy, the 7 year life-cycle of Red Hat Enterprise Linux AS/ES 2.1 has ended effective June 1, 2009. As such, Red Hat has discontinued the technical support services, bug fix, enhancement, and security errata updates for Red Hat Enterprise Linux AS/ES 2.1. For instructions on migrating Red Hat Enterprise Linux 2.1 or 3 to Red Hat Enterprise Linux 4, see OracleMetaLink Note 303237.1. For migrating an EBS 11i installation from Red Hat Enterprise Linux 2.1 to RHEL/OEL 5 see OracleMetaLink Note 850358.1. ²In accordance with the Sun End of Service Life (EOSL) support policy, the life-cycle of Solaris 6 (5.6) has ended. Customers are urged to migrate to a supported version of Solaris SPARC. ³In accordance with the Hewlett Packard Prior Version Support – Sustaining Engineering (PVS-SE) support policy, the life-cycle of HP Tru64 UNIX Versions 4.0F, 4.0G, and 5.1A has ended. Customers requiring support on patch kits or releases that are no longer supported should contact their HP Representative to determine if extended sustaining engineering support is available and under what terms and conditions such extended support may be purchased. Customers are urged to upgrade to the only currently supported HP Tru64 UNIX Version 5.1B. 4AIX 5.2 has been generally desupported by IBM – please see OracleMetaLink Note 803307.1 for more information. **For HP-UX Itanium, Rapid Install supports database tier installations for multi-node systems. You install the database tier on HP-UX Itanium and the application tier on HP-UX PA-RISC. The Oracle Applications 11i for HP-UX PA-RISC (32-bit) with Oracle9i for HP-UX Itanium bundle contains January 2006 Critical Patch Updates on both the database and application tiers. See the Multi-node Installations chapter inInstalling Oracle Applications: A Guide to Using Rapid Install for more information. |
|
Required Packages and Patches
The following table lists the packages and individual patches required for each operating system. Unless otherwise noted, the packages and patches must be installed manually.
| Additional Information:See the installation instructions (software and hardware requirements section) for information on the RDBMS-specific version for your platform. See also the vendor’s operating system installation manual or the operating system media for information on obtaining and applying patches. |
| Operating System | Required Patches |
| Oracle Enterprise Linux 4* | Quarterly Update 4 or higher (Recommended Version)
|
| Oracle Enterprise Linux 5*Red Hat Enterprise Linux 5* (base and Advanced Platform) | Update 1 (OEL 5.1) or higher is requiredUpdate 1 (RHEL 5.1) or higher is required.
The following packages are not part of the OEL 5 or RHEL 5 distribution media and must be installed manually:
The following packages must be installed from the OEL 5 or RHEL 5 distribution media:
Note : 1: Download from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux/ (for both OEL 5 and RHEL 5) |
| Red Hat Enterprise Linux AS/ES 2.1* |
|
| Red Hat Enterprise Linux AS/ES 3* | Quarterly Update 1 or higher (Minimum required version)Note: See Certify on OracleMetaLink for information on specific Quarterly Updates requirements. |
| Red Hat Enterprise Linux AS/ES 3* | Quarterly Update 4 (Recommended version)Note: From the Package Group Selection screen, select Legacy Software Development. The following components will be installed automatically:
The following required component must be installed manually:
Note: Available on Disk 3 of Quarterly Update 4 media. |
| Red Hat Enterprise Linux AS/ES 4* | Legacy Software Development package and X Software Development packageNote: Select these packages from the Package Group Selection screen. If the operating system is already installed, use System Settings > Add/Remove Applications to install these two packages.
The following components will be installed automatically:
The following required component must be installed manually:
Note: For information on downloading the openmotif component, see the instructions at the following URL:https://rhn.redhat.com/errata/RHSA-2 005-412.html |
| SUSE Linux Enterprise Server 8 | The following required components must be installed manually:
Note:
|
| SUSE Linux Enterprise Server 9 | The following required components must be installed manually:
Note:
|
| SUSE Linux Enterprise Server 10 | Service Pack 1 (SP1) or higher is required. The following components must also be installed manually:
Additionally, the following must be installed manually from the SLES 10 distribution media if not already on the system:
Note : 1: Download from the Novell site: ftp://ftp.novell.com/partners/oracle/ebiz11i |
| Solaris 8 (5.8), 9 (5.9) | J2SE Solaris Recommended Patch Cluster, dated 7/05/05 or later |
| HP-UX PA-RISC 11.11 | PHCO_25452, PHNE_25084, PHNE_25642, PHSS_24638 (C++), GOLDQPK11i-December 01, C++ Compiler C.03.27 (or higher) or HP C/aC++ Developer’s Bundle** |
| HP-UX PA-RISC 11.23, 11.31 | C++ Compiler A.03.60 (or higher) or HP C/aC++ Developer’s Bundle** |
| HP-UX Itanium 11.23, 11.31 | None |
| IBM AIX 5L (5.2, 5.3) | Visual Age C++ 6.0.0.5 (or higher) and Oct. 2003 PTF, or IBM XL 7.0 C/C++1,2 runtime libraries , or IBM XL 8.0C/C++1,2 runtime libraries. For other minimum software versions and patches required to support Oracle Products on IBM pSeries, see OracleMetaLink note (Doc ID: 282036.1).For installations on 32-bit kernel AIX 5.3 Technology Level (TL) 6 with Service Pack 4 and below, please install the APAR IZ05077 or use the 64-bit kernel. |
| IBM AIX 6 (6.1) | Service Pack 1 (AIX 6100-00-01) or higher. IBM XL 8.0 C/C++ (at least at the November 2007 PTF level – 8.0.0.17) runtime libraries. APAR IZ10223 (‘Olson Timezone settings is not working for 64-bit Applications’) for base level AIX (6100-00). |
| Windows 2000 | Service Pack 2. See also General Requirements for Windows. |
| Windows Server 2003 | None. See General Requirements for Windows. |
| Footnotes: *After installing these patches, run ldconfig -v.** Some Oracle Applications product modules (Discrete Manufacturing (WPS, WIP, ENG) and Advanced Planning & Scheduling (MSC, MSO, MSR)) are written in C++ and require the C++ compiler to perform the link. If the system where Oracle Applications is being installed has no other use for the C++ compiler, you can download and install the 60-day trial version of the HP C/aC++ Developer’s Bundle rather than purchasing the full C++ compiler. The linker included in the Developer’s Bundle does not expire and can be used beyond the 60-day trial limitation. For more information, review the HP C/aC++ FAQ here. 1 IBM XL 7.0C/C++ or IBM XL 8.0C/C++ is required for Discrete Manufacturing (WPS, WIP, ENG) and Advanced Planning & Scheduling (MSC, MSO, MSR). http://www-01.ibm.com/support/docview.wss?uid=swg24007696 (7.0) |
|
Split Configurations
After you have installed Oracle Applications, you can subsequently migrate the database tier of Oracle Applications to other operating systems. This is called a split configuration database tier.
For a list of operating systems available and instructions on how to create a split configuration database tier, refer to Oracle Certify on OracleMetaLink. From the main page, select View Certifications by Product > E-Business Suite > E-Business Suite > 11i Split Configuration Information.
Java 2 Standard Edition (J2SE)
Rapid Install installs the Java 2 Standard Edition 1.4.2 automatically for systems running on Solaris, Linux, or Windows operating systems. If your system runs on HP-UX PA-RISC, HP-Tru64, or IBM AIX, you must download and install J2SE before you continue with the installation or upgrade.
Step 1 Download Java 2 Standard Edition
J2SE 1.4 is available from a download site provided by your OS vendor. Use this site to download J2SE for the operating system on the node(s) where you deploy your application tier servers (forms, Web, concurrent processing, and administration servers).
| Note:Download the Java 2 Development Kit, Standard Edition, not the Java 2 Runtime Environment (JRE), Standard Edition. |
Find your application tier operating system in the following table. Go to the URL listed and download the latest available patch release provided. Maintenance releases are indicated by the third digit, such as 1.4.2. Patch releases are designated with the fourth set of numbers, such as 1.4.2.03.
| Operating System | Certified Version | Download Location |
| HP-UX PA-RISC | J2SE 1.4.2 | http://www.hp.com/products1/unix/java/ |
| HP-Tru64 | J2SE 1.4.2 | http://www.compaq.com/java/download/index.html |
| IBM AIX | J2SE 1.4.2* | http://www.ibm.com/developerworks/java/jdk/aix/index.html |
| *For AIX 5L, download JDK 1.4.2 release 20050609 or later. | ||
Step 2 Install J2SE on the application tier servers
Follow the instructions from the download site to install J2SE on each node that contains an application tier server. Note the new J2SE 1.4 installation top-level directory. Insert the full path as <JDK14_TOP> when instructed to do so.
| Note:Review the installation instructions and Release Notes for the J2SE you download to ensure that the OS version you are running is supported with J2SE 1.4. You may have to upgrade to a later, certified version of the OS or apply other system patches before you can install the J2SE. |
Step 3 Verify the installation
Type the following command to verify that you have installed the correct version:
<JDK14_TOP>/bin/java -version
The version should read “1.4.x.y”, where x is the certified maintenance level, and y is the patch level you installed. When the Rapid Install wizard prompts for the J2SE location, enter <JDK14_TOP>.
Discoverer
The Discoverer 4i product has been de-supported effective November 2006 and all Oracle E-Business Suite customers must upgrade to Discoverer 10g if they intend to use the Discoverer product with EBS. Please refer to OracleMetaLink Note: 313418.1 ‘Using Discoverer 10g with Oracle Applications 11i’.
Users should check Certify on OracleMetaLink for currently supported operating systems for the Discoverer 10g product.
General Requirements for UNIX/Linux
This section outlines requirements that apply to all UNIX/Linux operating systems. Specific requirements are listed under separate headings.
LD_LIBRARY_PATH Environment Variable
Dynamic libraries are used as part of the relinking and execution processes. The LD_LIBRARY_PATH environment variable is used by Oracle Applications to locate the required dynamic libraries at runtime. Rapid Install sets LD_LIBRARY_PATH as follows:
On each application tier server node:
LD_LIBRARY_PATH is set in three places:
- $APPL_TOP/admin/adovars.env
- $ORACLE_HOME/<CONTEXT_NAME>.env, in both the 8.0.6 and iAS Oracle home directories
To change the value in any of the application tier locations, use the Edit Parameters function of the OAM AutoConfig tool to update the following fields (as required). Then, run AutoConfig (adautocfg.sh) to implement the changes.
| Parameter | Value |
| adovars | LD_LIBRARY_PATH or SHLIB_PATH (HP-UX PA-RISC only) or LIBPATH (IBM AIX only) |
| iAS Oracle Home | LD_LIBRARY_PATH or SHLIB_PATH (HP-UX PA-RISC only) or LIBPATH (IBM AIX only) |
| Tools Oracle Home | LD_LIBRARY_PATH or SHLIB_PATH (HP-UX PA-RISC only) or LIBPATH (IBM AIX only) |
| Additional Information:See AutoConfig in Oracle Applications Maintenance Utilities. |
On the database server node:
LD_LIBRARY_PATH is set in $ORACLE_HOME/<CONTEXT_NAME>.env.
Linux x86 and Linux x86-64 (AMD64/EM64T) Requirements
This section describes requirements that are specific to Linux x86 and Linux x86-64 (AMD64/EM64T). Oracle Applications (11i) is supported on Linux x86 or Linux x86-64 (AMD64/EM64T) running the 32-bit version of the operating system only.
| Note:You can only install Oracle Applications on an x86-64 architecture server if the operating system is 32-bit Linux or Windows. If your operating system is 64-bit, contact your operating system vendor to obtain a 32-bit operating system before installing Oracle Applications. |
All Linux x86 and Linux x86-64 (AMD64/EM64T) Operating Systems
Oracle Enterprise Linux 4, Oracle Enterprise Linux 5, Red Hat Enterprise Linux AS/ES 2.1, Red Hat Enterprise Linux AS/ES 3, Red Hat Enterprise Linux AS/ES 4, Red Hat Enterprise Linux 5, SUSE Linux Enterprise Server 8, SUSE Linux Enterprise Server 9, SUSE Linux Enterprise Server 10 all have dependencies on the following components. Dependencies that pertain only to a subset of Linux x86 and x86-64 (AMD64/EM64T) operating systems are listed under separate headings.
Kernel Requirements
The following table lists the required minimum kernel versions (to determine version, enter: $ uname -r).
| Operating System | Kernel |
| Oracle Enterprise Linux 4 | 2.6.9-42.0.0.0.1.EL |
| Oracle Enterprise Linux 5 | 2.6.18-8.EL |
| Red Hat Enterprise Linux AS/ES 2.1 | 2.4.9-e.x (where x is > than 12) Note: In accordance with the Red Hat Enterprise Linux Errata Support Policy, the 7 year life-cycle of Red Hat Enterprise Linux AS/ES 2.1 has ended effective June 1, 2009. For instructions on migrating Red Hat Enterprise Linux 2.1 or 3 to Red Hat Enterprise Linux 4, see OracleMetaLink note (Doc ID: 303237.1). |
| Red Hat Enterprise Linux AS/ES 3 | 2.4.21-9.EL (required) 2.4.21-20.EL (recommended) |
| Red Hat Enterprise Linux AS/ES 4 | 2.6.9-5.EL |
| Red Hat Enterprise Linux 5 | 2.6.18-8.EL |
| SUSE Linux Enterprise Server 8 | 2.4.21-138 |
| SUSE Linux Enterprise Server 9 | 2.6.5-7.97 |
| SUSE Linux Enterprise Server 10 | 2.6.16.21-0.8 |
glibc Requirements
The following table lists the required minimum glibc versions (to determine this, enter: $ rpm -q glibc).
| Operating System | glibc |
| Oracle Enterprise Linux 4 | 2.3.4-2.25 |
| Oracle Enterprise Linux 5 | 2.3.4-2.26 |
| Red Hat Enterprise Linux AS/ES 2.1 | 2.2.4-32.3 Note: In accordance with the Red Hat Enterprise Linux Errata Support Policy, the 7 year life-cycle of Red Hat Enterprise Linux AS/ES 2.1 has ended effective June 1, 2009. For instructions on migrating Red Hat Enterprise Linux 2.1 or 3 to Red Hat Enterprise Linux 4, see OracleMetaLinknote (Doc ID: 303237.1). |
| Red Hat Enterprise Linux AS/ES 3 | 2.3.2-95.3 |
| Red Hat Enterprise Linux AS/ES 4 | 2.3.4-2 |
| Red Hat Enterprise Linux 5 | 2.3.4-2.26 |
| SUSE Linux Enterprise Server 8 | 2.2.5-213 |
| SUSE Linux Enterprise Server 9 | 2.3.3-98.28 |
| SUSE Linux Enterprise Server 10 | 2.4-31.2 |
Domain Name System (DNS) Resolver Parameters
Two Domain Name System (DNS) resolver parameters (timeout and attempts) are set by default to low values when the operating system is installed. These low values may cause attempted network connections to an Oracle database to fail. If this happens, add or update the following entries to these minimum settings in the /etc/resolv.conf file on each server node:
options attempts:5
options timeout:15
Net Service Listeners in Multi-user Installations
Give all users in a multi-user installation write privileges to the .oracle directory:
$ chmod 777 /var/tmp/.oracle
Oracle Enterprise Linux 4 and 5, Red Hat Enterprise Linux 3, 4 and 5 and SUSE Linux Enterprise Server 8, 9 and 10
This section describes requirements that apply only to Oracle Enterprise Linux 4 and 5, Red Hat Enterprise Linux 3, 4 and 5 and SUSE Linux Enterprise Server 8, 9 and 10.
Verifying Host Names
Use the following to verify host name settings:
For Oracle Enterprise Linux 4 and 5, Red Hat Enterprise Linux 3, 4 and 5:
- Verify that the /etc/hosts file is formatted as follows:
2. 127.0.0.1 localhost.localdomain localhost
3. <ip_address> <node_name>.<domain_name> <node_name>
- Verify that the /etc/sysconfig/network file is formatted as follows:
5. HOSTNAME=<node_name>.<domain_name>
- If the /etc/sysconfig/networking/profiles/default/network file exists, remove it.
- If you changed any files in the previous steps, restart the system.
For SUSE Linux Enterprise Server 8, 9 and 10:
- Verify that the /etc/hosts file is formatted as follows:
2. 127.0.0.1 localhost.localdomain localhost
3. <ip_address> <node_name>.<domain_name> <node_name>
- If you changed any files in the previous step, restart the system.
Modifying the Number of Open File Descriptors
Open the /etc/security/limits.conf file and change the existing values for “hard” and “soft” parameters as follows. Restart the system after making changes.
For Oracle Enterprise Linux 4 and 5, Red Hat Enterprise Linux 3, 4 and 5 and SUSE Linux Enterprise Server 9 and 10:
* hard nofile 65535
* soft nofile 4096
For SUSE Linux Enterprise Server 8:
* hard nofile 32768
* soft nofile 32768
Modifying the Port Range Values
Open the /etc/sysctl.conf file and change the value of net.ipv4.ip_local_port_range as follows. Restart the system after making changes.
net.ipv4.ip_local_port_range = 10000 65000
Please note that this range is a recommended range, and may need to be adjusted according to the specific needs of the user’s environment in order to avoid port conflicts.
Setting the Environment
Perform the following tasks to set the environment before you run Rapid Install.
- Rename the /usr/bin/gcc and /usr/bin/g++ files.
For Red Hat Enterprise Linux AS/ES 3 and SUSE Linux Enterprise Server 9 only:
# mv /usr/bin/gcc /usr/bin/gcc323
# mv /usr/bin/g++ /usr/bin/g++323
For SUSE Linux Enterprise Server 10 only:
# mv /usr/bin/gcc /usr/bin/gcc41
# mv /usr/bin/g++ /usr/bin/g++41
For SUSE Linux Enterprise Server 8 only:
# mv /usr/bin/gcc /usr/bin/gcc322
# mv /usr/bin/g++ /usr/bin/g++322
- Create symbolic links.
For Red Hat Enterprise Linux AS/ES 3 only:
# ln -s /usr/bin/gcc296 /usr/bin/gcc
# ln -s /usr/bin/g++296 /usr/bin/g++
For SUSE Linux Enterprise Server 8, 9 and 10 only:
# ln -s /opt/gcc295/bin/gcc /usr/bin/gcc
# ln -s /opt/gcc295/bin/g++ /usr/bin/g++
For SUSE Linux Enterprise Server 10 only:
# ln -s /usr/bin/ld215 /usr/bin/ld
# ln -s /usr/lib/libdb.so.2 /usr/lib/libdb.so.3
# ln -s /usr/lib/libgdbm.so /usr/lib/libgdbm.so.2
For Oracle Enterprise Linux 5 and Red Hat Enterprise Linux 5 only :
# ln -s /usr/bin/ld215 /usr/bin/ld
Download and apply the OS library patch 6078836 from OracleMetaLink and create the following symbolic link:
# ln -s /usr/lib/libdb.so.2 /usr/lib/libdb.so.3
- Verify that the host name setting is correct. The command should return a fully qualified host name. For example: <host_name>.<domain_name>.
# hostname -f
Completing Preinstallation Tasks
Complete these tasks after you set the environment variables and before you begin the installation steps described in Installing Oracle Applications.
- Unset the NLS_LANG environment variable, if it is defined prior to installation.
- For Red Hat Enterprise Linux 3, apply the OS library patch 3006854 (downloadable from OracleMetaLink).
- For Oracle Enterprise Linux 5, Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10 customers, the LD_ASSUME_KERNEL environment variable should be unset before starting the installation. The installation fails when the LD_ASSUME_KERNEL variable is set by the adgetlnxver.sh file during the course of the installation. Patch 6365595 contains the fix for adgetlnxver.sh file. The procedure below is a guideline for replacing the adgetlnxver.sh file in the Oracle Applications 11i shiphome.
- Download the patch 6365595 from OracleMetalink.
- Follow the Oracle Applications Installation guide and set up the stage area.
- Set the STAGE_TOP environment variable to the top level directory of the stage area that contains the subdirectories startCD, oraApps, oraDB, oraiAS and oraAppDB. Make sure that the stage area is read writable.
- Create the following directories in the stage area.
# mkdir -p $STAGE_TOP/oraDB/Disk3/db/stage/appsutil/bin
# mkdir -p $STAGE_TOP/oraApps/Disk5/appl/stage/bin - Copy the adgetlnxver.sh file in the patch 6365595 to the following directories created in earlier step.
# cp -p 6365595_PATCH_TOP/ad/bin/adgetlnxver.sh $STAGE_TOP/oraDB/Disk3/db/stage/appsutil/bin
# cp -p 6365595_PATCH_TOP/ad/bin/adgetlnxver.sh $STAGE_TOP/oraApps/Disk5/appl/stage/bin - Update the zip archive with the fix (adgetlnxver.sh file).
# cd $STAGE_TOP/oraDB/Disk3/db/stage
# zip -u dboh0_appsutil appsutil/bin/adgetlnxver.sh
# cd $STAGE_TOP/oraApps/Disk5/appl/stage
# zip -u ad_CORE bin/adgetlnxver.sh - For Oracle Enteprise Linux and Red Hat Enteprise Linux 5 Update 3 (5.3), users will see a failure when running Rapid Install. Users must edit the file $STAGE_TOP/startCD/Disk1/rapidwiz/bin/runWizard.sh and comment out lines 122-125, as in:
5. # if test “$exit_code” == “0″ ; then
# LD_ASSUME_KERNEL=2.4.19
6. # export LD_ASSUME_KERNEL
# fi
- Restart your system
Completing Postinstallation Tasks
After the installation is complete, perform the following tasks in addition to the ones described in Installing Oracle Applications:
- For Oracle Enterprise Linux 4, Red Hat Enterprise Linux AS/ES 2.1, 3 and 4 and SUSE Linux Enterprise Server 8 and 9 only:
Apply patch 4632932 to all the application tiers, then re-source the applications environment file to refresh the environment variables. - For Oracle Enterprise Linux 5, Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10 only:
Apply patch 6365595 to all the application tiers, then re-source the applications environment file to refresh the environment variables. - Oracle Database Server 9i is not supported on Oracle Enterprise Linux 5, Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10. Follow the instructions in OracleMetaLink note 362203.1 and upgrade your database to 10g Release 2
Solaris SPARC Requirements
This section describes requirements that are specific to Solaris SPARC.
Net Service Listeners in Multi-user Installations
Give all users in a multi-user installation write privileges to the .oracle directory:
$ chmod 777 /var/tmp/.oracle
Rotate Logs Shutdown
If you are experiencing intermittent shutdown delays with the rotate logs feature in Oracle 9iAS, apply Oracle Critical Patch Update July 2005 for Oracle Application Server (patch 4393827) or superseding patch to resolve this issue..
RDBMS Language Files
If you have installed a 64-bit RDBMS either with a full installation of Oracle Applications release 11.5.10.2 or by using the ‘rapidwiz -techstack’ command of Rapid Install, you must download and apply patch 5354588 to your release 9.2.0 Oracle home.
HP-UX PA-RISC Requirements
This section describes requirements that are specific to HP-UX PA-RISC.
Kernel Settings
The following table lists the recommended kernel parameter settings for all HP-UX PA-RISC versions.
| Parameter | Value |
| maxdsiz | 0xC0000000 -> 3 Gbyte |
| maxssiz | 0×04000000 -> 64 Mbyte |
Note: Failure to set the above kernel parameters to the recommended values may result in allocate memory problems when running Oracle Applications programs.
Refer to your operating system documentation or contact your operating system vendor for more information on how to set kernel parameters.
Net Service Listeners in Multi-user Installations
Give all users in a multi-user installation write privileges to the .oracle directory:
$ chmod 777 /tmp/.oracle
Optimized ILOG Libraries
ILOG libraries must be optimized for the PA-RISC 1.1 architecture to increase performance for products based on C++ (MSO, WPS, WIP, ENG, and MRP). The default libraries are already optimized for PA-RISC 2.0, and are located in the $SHT_TOP/lib/ilog/5.1 directory on all servers except the RDBMS.
If your servers use PA-RISC 1.1 architecture, replace the default libraries with the PA-RISC 1.1 versions. The ILOG libraries are available in SHT patch 4297568.
To verify the PA-RISC version, type the following command. It produces a numeric output that identifies PA-RISC versions.
$ /usr/bin/getconf
_SC_CPU_VERSION
The following table describes the output and lists the appropriate action.
| Output | Version | Action |
| 528 | PA-RISC 1.1 | Replace ILOG libraries with PA-RISC 1.1 version. (patch 4297568) |
| 529 | PA-RISC 1.1 | Replace ILOG libraries with PA-RISC 1.1 version. (patch 4297568) |
| 532 | PA-RISC 2.0 | No action required |
You can ignore any relinking errors when applying patches on other nodes that do not have the C++ Compiler.
HP-Tru64 Requirements
This section describes requirements that are specific to HP-Tru64.
Net Service Listeners in Multi-user Installations
Give all users in a multi-user installation write privileges to the .oracle directory:
$ chmod 777 /tmp/.oracle
Perl Requirement
Oracle recommends using Perl 5.6.x or higher for the Applications Server (iAS). After you install Perl, see OracleMetaLink note (Doc ID: 218089.1) for instructions on how to run AutoConfig to reconfigure your instance to use the new Perl.
ulimit for Data Area
For all nodes, check the size of the resource limit of the data area and the virtual memory with these commands:
$ ulimit -d
$ ulimit -v
If the size of the data area is smaller than the size of the virtual memory, increase the data area to the same as the virtual memory. For example, if you are using a Korn shell, set the ulimit data area size to 1048576 KB by running this command:
$ ulimit -d 1048576
IBM AIX Requirements
This section describes requirements that are specific to AIX.
Net Service Listeners in Multi-user Installations
Give all users in a multi-user installation write privileges to the .oracle directory:
$ chmod 777 /tmp/.oracle
Kernel Extensions
Read and follow all the instructions in the AIX-KERNEL-EXT-README in the Oracle Applications 11i Release 11.5.10.2 Rapid Install Start Here DVD before you run Rapid Install. The readme file is located in the aix_preInstall directory (startCD/Disk1/rapidwiz/oui/IBM_AIX/aix_preInstall).
The instructions in the readme file tells users to run the preInstaller.sh which in turn requires the superuser (root) to run a provided rootpre.sh script.
| Note:Installation on an AIX 6 (6.1) system requires an updated rootpre.sh file along with associated files for use with 10gR2 of the database. AIX 6 users must install the database patch 6613550 available from OracleMetaLinkprior to installing EBS 11i on an AIX 6 system.
Please backup the contents of the aix_preInstall directory and then overwrite the contents of the directory with the content of the above database patch before running the new rootpre.sh. |
| Note:Prior to running the 11.5.10.2 Rapid Install on AIX (5L or 6), you must download and install the startCD patch 8606387 (available from OracleMetaLink) to the 11.5.10.2 staging area. |
Data Segment Size
You must have 1 GB of data segment size available for relinking MSC, MSO, and MSR product executables. To check the current size, run the following command:
$ dump -X64 -o /usr/ccs/bin/bind64
If the last line returns 0×00000000 for maxDATA, the current maximum size is 256 MB (the default for AIX 32-bit applications). To set the data segment size to 1 GB, set the LDR_CNTRL variable to LDR_CNTRL=MAXDATA=0×40000000@DSA.
Set Environment variable to avoid Forms Generation executable crashes
When generating large form files through AD Administration or applying a patch, the Forms generation executable can crash and form files fail to be generated. This problem is caused by the size of the form files increasing and the memory space being allocated. To work-around this problem, set the environment variable LDR_CNTRL to MAXDATA=0×40000000@DSA.
For example (in ksh):
$ export LDR_CNTRL=MAXDATA=0×40000000@DSA
General Requirements for Windows
This section describes requirements that apply to all supported Windows operating systems. Requirements for specific operating systems are listed under separate headings.
| Note:The information in this section addresses the operation of the database tier and the application tier servers only. See OracleMetaLink for information about client desktop issues. |
Syntax and Environment Variables in User Documentation
User documentation examples use a command prompt syntax and make use of environment variables. This syntax is used in all documentation associated with installing, upgrading, or maintaining your system. If an example makes reference to an environment variable %<var_name>%, check to see if it is set in the environment:
C:\> echo %<var_name>%
For example, if the <var_name> is GL_TOP, and echo %GL_TOP% returns a valid path name, you can use GL_TOP on the command line:
C:\> cd
%GL_TOP%\admin\sql
Install XML Parser
On Windows platforms, Rapid Install requires Microsoft XML Parser 3.0 Service Pack 4 (or later) in order to set up and start services. Before you begin your installation, follow these steps to determine if the correct version of the XML Parser is installed on your system, and take action as necessary.
- Open the Windows Explorer
- Navigate to the system root directory (default is C:\winnt\system32).
- Right-click msxm13.dll. Select Properties. them click Version.
- If XML Parser is not already installed, or if the version on your system is not 3.0 SP4 (or later), go to the following URL and download the Microsoft XML Parser 3.0 SP4 Software Development Kit:
- After installing MSXML 3.0 SP4 SDK, copy msxm12.lib from <Microsoft XML Parser SDK>\lib to <Visual C++/C>\lib, where <Microsoft XML Parser SDK> is the installed location of the MSXML 3.0 SP4 SDK, and <Visual C++/C> is the installed location of Visual C++/C 6.0.
Release Maintenance Tools
Users are expected to acquire and install the release maintenance tools listed in this section. Follow these guidelines when installing the target installation directories:
- Do not install the tools in the Program Files directory, or any other target directory with blank spaces in its name.
- Do not install the tools under the APPL_TOP.
You will encounter problems relinking if the executables are in a \bin directory under any of the Oracle Applications product tops. Make sure each of the executables is in the PATH after installation.
Microsoft Visual C++ (MS VC++)
Version 6.0 + Service Pack 3 or higher. Visual C++.NET editions, available separately or as part of Visual Studio, are not supported. SeeHow to Obtain Visual C++ for Release 11i on Windows on OracleMetaLink (Doc ID: 201392.1) for information on obtaining this software.
This tool is required to be installed on the application tier only.
MKS Toolkit
Version 6.1a or higher. You can use any of the Developer series (for Developers, for Professional Developers, or for Enterprise Developers). You can obtain this software from the MKS Web site at http://www.mks.com.
This tool is required for both the application and database tiers running Windows.
| Note:While MKS Toolkit is recommended, Cygwin can now be used in its place. See “Using Cygwin to Maintain Release 11i on Windows” on OracleMetaLink (Doc ID: 302859.1) for information. |
GNU make (Shareware)
Version 3.77 or higher, excluding 3.79.0. See GNU Make Requirement for Release 11i for Windows on OracleMetaLink (Doc ID: 268776.1) for information.
This tool is required to be installed on the application tier only.
Read-only Directory
If you run Rapid Install from a read-only media/shiphome, AutoConfig may report an error while executing the txkGenExtSecConf.pl script. Check the log file for AutoConfig errors after you finish running Rapid Install. If this error is reported, run AutoConfig from a writable directory to correct the problem.
| Additional Information:See AutoConfig in Oracle Applications Maintenance Utilities. |
Oracle Alert
Your system must meet the requirements in this section to use Oracle Alert.
Exchange Server
Oracle Alert requires Exchange Server 2000 or higher.
Windows Messaging
Windows Messaging, also known as Messaging Application Programming Interface (MAPI), is required. You can install Microsoft Outlook 2000 to obtain Windows Messaging, or you can obtain it directly from Microsoft Support. See Microsoft Web document Q254458 at:
http://support.microsoft.com/support/kb/articles/Q254/4/58.asp
| Note:Windows Messaging is supplied without product support. |
Outlook E-mail Security Update
Do not apply the Outlook E-mail Security Update. If it has already been applied, follow the instructions in Microsoft Web document Q263444 at:
http://support.microsoft.com/support/kb/articles/Q263/4/44.asp
Compressed Disk Drives
Do not use compressed drives for installing any of the Oracle Applications Release 11i components. Patching and relinking will not work correctly on a disk drive that is compressed.
Windows Services
If the concurrent manager service is running on the same node as the database, it may not start automatically after a restart. If that happens, make sure that the database service (ORACLEService<SID>) is running and the TNS listener (ORACLE<SID>_<DB_VERS>_RDBMSTNSListener<SID>) has started. Then, use the Service Control Panel to start the concurrent manager.
There are a number of technology stack services created by Rapid Install that are not currently used by Oracle Applications. They are set to start manually. There is no need to start these services or to change them to start automatically.
Default Debugger
See Default Debugger on Windows NT/2000 on OracleMetaLink (Doc ID: 136627.1) for information on setting up the default debugger.
Remote Installation
Oracle Corporation does not explicitly test or support the installation of E-Business Suite products from remote clients (such as Terminal Services Client). We recommend that you install directly on the computer console, or by connecting to a console session using tools such as pcanywhere (from pcanywhere.com), vnc (from vnc.com), or Windows 2003 Terminal Services (available for Windows Server 2003 only).
| Additional Information:For instructions on using Windows 2003 Terminal Services, see Microsoft Knowledge Base Article 278845. |
Windows Server 2003 Requirements
The requirements in this section pertain only to Windows Server 2003 editions.
Unsupported Products
The following products are currently not supported for Windows Server 2003 editions:
- Oracle eMail Center
- Oracle Field Service/Handheld
- Oracle Field Service/Laptop
Current Revisions Log
The following sections were changed in the Oracle Applications Installation Update Notes Release 11i (11.5.10.2).
| Section | Summary of Changes |
| Oct 2009 | Added recommended kernel settings for HP-UX |
| Sep 2009 | Added reference to new ML Note 850358.1 for migrating 11i from RHEL 2.1 to OEL/RHEL 5. Added clarification on the maintenance tools requirements regarding application and database tiers. |
| June 2009 | Added desupport of AIX 5.2; added AIX XL C/C++ runtime libraries links since full compiler is not required; added reference to startCD patch 8606387 required for all AIX to remove checks for a full compiler (which includes previous fix for AIX 6 only – 7042287 ) |
| June 2009 | Update to reflect desupport of Red Hat Enterpise Linux AS/ES 2.1, HP Tru64 4.0F/4.0G/5.1A, and Solaris SPARC 6 (5.6) |
| April 2009 |
|
| January 2009 | Adjusted ip_local_port_range to 10000 -> 65000 |
| October 2008 | Added openmotif and orarun rpms for SLES 10 to be installed from the media manually if necessary. |
| August 2008 | Modify OEL5/RHEL5 list of packages; remove xorg packages and add libXp package. |
| August 2008 | Added missing HP-UX 11.31 references. |
| July 2008 | Added workaround for Forms generation failure on AIX; added more specific information on download locations for OEL/RHEL 5 rpms. |
| June 2008 | Added support for AIX 6 (6.1). Added Discoverer 4i de-support info and removed Disco 4i setup instructions. Added additional SLES10 package info (gdbm). |
| May 2008 | Added support for OEL/RHEL 5 and SLES 10 |
| Jan 2008 | Fixed the compat-libcwait rpm entries for OEL/RHEL 4 |
| Nov 2007 | Added requirement for 32-bit AIX 5.3 with TL-6 to install an APAR |
| October 2007 | Added information regarding use of the HP C/aC++ Developer’s Bundle on HP-UX for linking. |
| September 2007 | Added Oracle Enterprise Linux 4.0 to list of supported Linux x86 OS’es. |
| August 2007 | Removed reference of HP-UX PA-RISC/HP-UX Itanium bundle being packaged with the UTF8 character set Corrected the parameters for the Linux hostname command to determine the fully qualified hostname |
| April 2007 | Updated supported operating systems versions. Updated the .oracle directory for Net Service Listeners in Multi-user Installations. Modification of Software Requirements for HP-UX PA-RISC, IBM AIX and Linux. |
| March 2007 | Modification of the Linux Open File Descriptors and IBM AIX Data Segment Size. |
| September 2006 | Modification of C/C++ compiler information for HP, IBM AIX, and Solaris, modification of note about x86-64 architecture to include Windows, and modification of RDBMS Language Files paragraph to include “Rapid Install.” |
| June 2006 | Inclusion of note stating that users can only install Oracle Applications on a Linux x86-64 server running a 32-bit operating system. Inclusion of section describing split configurations. |
| April 2006 | Inclusion of Critical Patch Updates on both the database and application tiers for HP-UX Itanium bundles. |
| December 2005 | Certification of SUSE Linux Enterprise Server 8 and Enterprise Server 9. |
| July 2005 | Initial release of 11.5.10.2 (CU2) |
Oracle Applications Installation Update Notes, Release 11i (11.5.10.2) for Linux x86, Solaris SPARC, Microsoft Windows, HP-UX PA-RISC, HP-Tru64, IBM AIX
Copyright © 2003, 2009, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
Cloning Oracle Applications 11i with Rapid Clone
Cloning Oracle Applications Release 11i
|
| Note: Rapid Clone is currently not supported on Windows Itanium, Windows x86-64 (AMD64/EM64T) and HP OpenVMS Alpha. |
| Attention: Windows users. This document typically uses UNIX syntax when specifying directories; Please substitute the appropriate Windows syntax |
- Section 1: Prerequisites
Tasks to perform before using Rapid Clone. - Section 2: Clone Oracle Applications 11i
Tasks to prepare, copy, configure, and verify a cloned Applications System. - Section 3: Finishing Tasks
Tasks to complete the cloning process. - Section 4: Advanced Cloning Methods
Tasks for advanced options such as refreshing and multi-node cloning.
Conventions
|
|
Convention | Meaning |
|
|
Source system | Applications system being cloned. |
|
|
Target system | Applications system being created as a copy of the source. |
|
|
APPLMGR | User which owns the applications file system (APPL_TOP and application tier technology stack) |
|
|
ORACLE | User which owns the database file system (RDBMS ORACLE_HOME and database files). |
|
|
CONTEXT_NAME | The CONTEXT_NAME variable refers to the name of the Applications Context file. For systems installed with Rapid Install 11.5.8 or earlier, this value will typically be set to <SID>. For new AutoConfig or Rapid Clone customers, CONTEXT_NAME will be set to <SID>_<HOSTNAME>. |
|
|
Monospace Text |
Represents command line text. Type this command exactly as shown. |
|
|
< > | Text enclosed in angle brackets represents a variable. Substitute a value for the variable text. Do not type the angle brackets. |
Section 1: Prerequisites
Before cloning, prepare the source system by applying patches and running AutoConfig.
- Verify source and target nodes software versions
In addition to the Oracle Applications software requirements (see Installing Oracle Applications Release 11i Part No. B10638-01), the following software component versions must exist on the source and/or target nodes. The location column indicates the node where the software component must be present.
| Software | Minimum Version | Location | Details |
|
|
|
|
|
| Oracle Universal Installer | 2.2.0.19 | All source system nodes | Apply OUI22 patch 5035661 on every iAS and RDBMS ORACLE_HOME to be cloned. Do not apply the patch to your RDBMS ORACLE_HOME, if you have Oracle 10g or higher installed. |
| Perl | 5.005 | Source and target database nodes | Use the Perl shipped with iAS1022 and RDBMS 9i if available or download it from Perl.com. Perl must be in the PATH before cloning. Windows users: do not use Perl from MKSToolKit. |
| JRE | 1.1.8 | Source database node | If the RDBMS ORACLE_HOME was not installed using Rapid Install, install JRE 1.1.8 into the <RDBMS ORACLE_HOME>/jre/1.1.8 directory. |
| JRE | 1.3.1 | Source database node | Windows users only: install JRE 1.3.1 into the <RDBMS ORACLE_HOME>/jre/1.3.1 directory. See Appendix A for installation instructions. |
| JDK | 1.3.1 | Target middle-tier applications nodes | Refer to Upgrading to JDK 1.3 with Oracle Applications 11i on OracleMetaLink for instructions. |
| Zip | 2.3 | All source nodes | Download from InfoZip. Zip must be in your PATH for cloning. |
| OS utilities | N/A | All target nodes | OS utilities (see 11i Install Manual) must be in the the PATH when running adcfgclone.pl (Unix: make,ld,cc,ar – Windows: gnumake,link,cc,cmd) |
- Apply the latest AD Minipack
Apply patch 4712852 (AD.I.4) or higher.
Please refer to OracleMetaLink to obtain the latest MiniPack available for AD. - Windows users only:
Apply patch 2237858 to enable long file names support. - Apply the latest AutoConfig Template patch
Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes.
Please refer to document 165195.1 on OracleMetaLink to obtain the latest Autoconfig165195.1 on OracleMetaLink to obtain the latest Autoconfig Template Rollup Patch available. - Apply the latest Rapid Clone patches
Update the Oracle Applications file system with the latest Rapid Clone files by applying the following patches to all application tier server nodes : - Setup Rapid Clone on the Applications Tier
-
- If the source Applications system was created with Rapid Install version 11.5.5 or earlier and has not been migrated to AutoConfig, follow the instructions Migrating to AutoConfig on the Applications Tier Migrating to AutoConfig on the Applications Tier in document 165195.1 on OracleMetaLink).
- All users must run AutoConfig on the Applications Tier (see section 5: Maintaining System Configuration Maintaining System Configuration in document 165195.1 on OracleMetaLink).
- Setup Rapid Clone on the Database Tier
Implement AutoConfig in the RDBMS ORACLE_HOME (Follow the instructions in section Migrating to AutoConfig on the Database Tier Migrating to AutoConfig on the Database Tier in document 165195.1 on OracleMetaLink).
| Attention: Every time that a new Rapid Clone or Autoconfig patch is applied on the APPL_TOP, the RDBMS ORACLE_HOME must be updated with the files included on those patches. Follow the instructions in section Maintaining System Configuration Maintaining System Configuration in document 165195.1 on OracleMetaLink to synchronize the Rapid Clone and Autoconfig files on the RDBMS ORACLE_HOME. |
- Maintain Snapshot information
Log in to each Application Tier Node as the APPLMGR user and run Maintain Snapshot information in AD Administration.
See Oracle Applications Maintenance Utilities for more information.
Section 2: Clone Oracle Applications 11i
Use Rapid Clone to create template files for cloning on the source system. After the source system is copied to the target, Rapid Clone updates these templates to contain the new target system configuration settings. Rapid Clone will not change the source system configuration.
There are three phases to the cloning process:
- Prepare the Source System
Execute the following commands to prepare the source system for cloning.- Prepare the source system database tier for cloning
Log on to the source system as the ORACLE user and run the following commands:
cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>
perl adpreclone.pl dbTier - Prepare the source system application tier for cloning
Log on to the source system as the APPLMGR user and run the following commands on each node that contains an APPL_TOP:
cd <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>
perl adpreclone.pl appsTier
- Prepare the source system database tier for cloning
- Copy the Source System to the Target System
Copy the application tier file system from the source Applications system to the target node by executing the following steps in the order listed. Ensure the application tier files copied to the target system are owned by the target APPLMGR user, and that the database tier files are owned by the ORACLE user.- Copy the application tier file system
Log on to the source system application tier nodes as the APPLMGR user.- Shut down the application tier server processes
- Copy the following application tier directories from the source node to the target application tier node:
<APPL_TOP><OA_HTML><OA_JAVA><OA_JRE_TOP><COMMON_TOP>/util<COMMON_TOP>/clone<COMMON_TOP>/_pages(when this directory exists)<806 ORACLE_HOME><iAS ORACLE_HOME>
- Copy the database tier file system
Log on to the source system database node as the ORACLE user.- Perform a normal shutdown of the source system database
- Copy the database (DBF) files from the source to the target system
- Copy the source database ORACLE_HOME to the target system
- Start up the source Applications system database and application tier processes
- Copy the application tier file system
| Note: Unix/Linux users, make sure that the softlinks are preserved when copying. |
- Configure the Target System
Execute the following commands to configure the target system. You will be prompted for the target system specific values (SID, Paths, Ports, etc)- Configure the target system database server
Log on to the target system as the ORACLE user and type the following commands to configure and start the database:
cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
perl adcfgclone.pl dbTier - Configure the target system application tier server nodes
Log on to the target system as the APPLMGR user and type the following commands:
cd <COMMON_TOP>/clone/bin
perl adcfgclone.pl appsTier
- Configure the target system database server
| Attention: Windows user only: add <806 ORACLE_HOME>\bin to the system path before running this step. |
Section 3: Finishing Tasks
This section lists tasks that may be necessary depending on your implementation and the intended use of the cloned system.
- Update profile options
Rapid Clone updates only site level profile options. If any other profile options are set to instance specific values, you must update them manually. - Update printer settings
If the new cloned system needs to utilize different printers, update the target system with the new printer settings now. - Update workflow configuration settings
Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the target system.
| Table Name | Column Name | Column Value Details |
| WF_NOTIFICATION_ATTRIBUTES | TEXT_VALUE | Value starts with http://<old web host> : Update to new web host |
| WF_ITEM_ATTRIBUTE_VALUES | TEXT_VALUE | Value starts with “http://<old web host> : Update to new web host |
| WF_SYSTEMS | GUID | Create a new system defined as the new global database name using the Workflow Administrator Web Applications responsibility. |
| WF_SYSTEMS | NAME | Value needs to be replaced with the database global name |
| WF_AGENTS | ADDRESS | Update database link with the new database global name. |
| FND_FORM_FUNCTIONS | WEB_HOST_NAME | Update with the new web host name |
| FND_FORM_FUNCTIONS | WEB_AGENT_NAME | Update to point at the new PLSQL listener name |
| FND_CONCURRENT_REQUESTS | LOGFILE_NAME | Update with the correct path to the logfile directory |
| FND_CONCURRENT_REQUESTS | OUTFILE_NAME | Update with the new directory path on the target system |
- Verify the APPLCSF variable setting
Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory for concurrent manager log and output files) points to an acceptable directory. To modify it, change the value ofs_applcsfin the contextfile and run AutoConfig. - Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
If the target system is in a different domain name than the source system and SESSION_COOKIE_DOMAIN was not null in the source system, update that value to reflect the new domain name. - Windows users only reboot the target machine
Once cloning is completed reboot to enable the services.
Section 4: Advanced Cloning Options
This section describes advanced cloning procedures.
- Refreshing a target system
You may need to refresh the target system periodically to synchronize it with changes from the source.
To refresh the target system, perform the following steps as described in previous sections:
-
- Prepare the Source System
- Copy the Source System to the Target System
- Copy the application tier file system if the APPL_TOP, 806 ORACLE_HOME, or iAS ORACLE_HOME needs to be refreshed. Copy the portion of the application tier file system which has been updated.
- Copy the database tier file system if the RDBMS ORACLE_HOME or the database needs to be refreshed. If refreshing the database, the ORACLE_HOME should be refreshed at the same time.
- Configure the Target System
Specify the existing target system context file when running adcfgclone.pl commands:perl adcfgclone.pl dbTier <Database target context file>
where database context file is:
<RDBMS ORACLE_HOME>/appsutil/<Target CONTEXT_NAME>.xmlperl adcfgclone.pl appsTier <Appltop target context file>
where appltop context file is:
<APPL_TOP>/admin/<Target CONTEXT_NAME>.xml
- Finishing Tasks
- Cloning a single-node system to a multi-node system
This procedure allows the original single-node system to be cloned into a multi-node system. An Applications system comprises five server types:
-
- Database server (database tier)
- Forms server (application tier)
- Web server (application tier)
- Concurrent Processing server (application tier)
- Administration server (application tier)
During the single-node to multi-node cloning process, each of these servers can be placed on its own node, resulting in a multi-node target system.
-
- Perform prerequisites
Perform these steps on all source and target nodes. - Clone Oracle Applications 11i
Prepare, copy and configure the cloned Applications System. When creating more than one application tier server node from a single node system, the copy and configure steps must be performed on each target node. You can specify the server type for each target node while answering the prompts during the configuration step.
The database ORACLE_HOME and database only need to be copied to the node on which the database will be run. - Finishing Tasks
- Perform prerequisites
| Note: Another way of changing a single-node system to a multi-node system is to share the APPL_TOP. See document 233428.1 on OracleMetaLink document 233428.1 on OracleMetaLink for details. |
- Cloning a multi-node system to a multi-node system with same number of nodes
A multi-node system can be cloned provided the number of nodes and distribution of servers in the target system matches that of the source system.
To clone a multi-node system to a multi-node system, perform the cloning process on each node. For example, if the source system contains three nodes, perform the cloning process three times.
-
- Clone source system node 1 to target system node 1.
- Clone source system node 2 to target system node 2.
- Clone source system node 3 to target system node 3.
| Attention: The database server node must be cloned first. |
- Adding a new node to an existing system
You can use Rapid Clone to clone a node and add it to the existing Application System. The new node will run the same or a subset of the server types running on the source node. Follow the instructions in the Application Tier part of Clone Oracle Applications 11i:- Prepare the source system, copy it to the new node and configure it.
- After adcfgclone.pl completes, source the Applications environment and run the following commands on the target system:
- cd <COMMON_TOP>/clone/bin
- perl adaddnode.pl
| Note: If the SQL*Net Access security is enabled in the existing system (enabled by default from 11i10), you first need to authorize the new node to access the database through SQL*Net. See Managed SQL*Net Access from HostsManaged SQL*Net Access from Hosts in document 281758.1 on OracleMetalink for instructions on how to achieve this from OAM. |
- Reducing the number of nodes of a multi-node system (merge APPL_TOP)
You can use Rapid Clone to clone a multi-node system to a single-node system (or a multi-node system with fewer nodes) by merging the APPL_TOPs filesystem together. Follow the procedure for Merging existing APPL_TOPs in document 233428.1 Merging existing APPL_TOPs in document 233428.1 on OracleMetaLink. - Cloning a RAC system
You can use Rapid Clone to clone a RAC system. While cloning, you have the possibility to remove or add nodes to the cluster in the target RAC system. To clone a RAC system, perform the following tasks:
-
- Verify the prerequisites
- Apply TXK patch 3571388 (AutoConfig support for Oracle RAC instances)
- Migrate the source system cluster ORACLE_HOMES to AutoConfig as documented in document 165195.1 on OracleMetaLinkdocument 165195.1 on OracleMetaLink
- Prepare the Source System
Choose one of the ORACLE_HOMEs on the source cluster. This ORACLE_HOME will be used as a master to create all the target cluster system ORACLE_HOME. Run “perl adpreclone.pl dbTier” on it.
- Verify the prerequisites
| Note: You also have the option to clone each ORACLE_HOME from the source RAC cluster to the target cluster. In that case, run adpreclone.pl on every ORACLE_HOME. |
-
- Copy the Source System to the Target System
- Copy the master ORACLE_HOME from the source system to each node that will compose the target cluster. For example, if your source RAC system had 2 nodes, and you want to clone it to a 3 node target RAC system, you should copy the source master ORACLE_HOME to the 3 nodes on the target system.
- Copy the database files from the source to target system.
- Configure the Target System
- Log on to any ORACLE_HOME in the target cluster and run
adcfgclone.pl dbTier
- Log on to any ORACLE_HOME in the target cluster and run
- Copy the Source System to the Target System
This step configures the first node of the target system RAC cluster and recreates the database control files. The prompts, however, will gather information about every node in the target RAC cluster and the data will be re-used when configuring each subsequent node in the next step.
-
-
- For each remaning RDBMS ORACLE_HOME in the target system, run the following command as the ORACLE file system owner:
adcfgclone.pl dbTier
- If your database is version 10g or higher, run the following commands to register the database and the instance to the cluster manager .
srvctl add database -d <database_name> -o <oracle_home>srvctl add instance -d <database_name> \
-i <instance_name> -n <host_name>
- For each remaning RDBMS ORACLE_HOME in the target system, run the following command as the ORACLE file system owner:
-
| Note: If the cluster manager is not on Linux (ORACM) or the database is version 10g or higher, manually start up the cluster manager on the target system before running adcfgclone.pl |
-
- Clone the application tier
Follow the steps in section 2 to prepare, copy and configure the application tier. When prompted for the database SID, specify any one of the RAC service names.
- Clone the application tier
| Note: To clone from RAC to non-RAC, follow the same above steps but copy the master ORACLE_HOME to one target node only, and answer “No” to the question “Target instance is a Real Application Cluster (RAC) instance (y/n)”, when prompted by adcfgclone.pl. |
- Adding a node to an existing RAC Cluster
You can use Rapid Clone to add one or several nodes to an existing RAC Cluster. Perform the following tasks:- Choose any one of the ORACLE_HOMEs in the existing cluster and run “perl adpreclone.pl dbTier” on it. This ORACLE_HOME will be used as a master to create the additional node(s).
- Copy the master ORACLE_HOME filesystem to the new node(s).
- Reconfigure the RAC Cluster to include the new node(s):
- Log on to the new node, or any one of the new nodes if adding more than one, and run the following command:
cd /appsutil/clone/binperl adcfgclone.pl dbTier
- Log on to the new node, or any one of the new nodes if adding more than one, and run the following command:
| Note: You will be prompted for information about all the nodes forming the new cluster and asked to perform the next step before completing adcfgclone.pl on this node. |
-
-
- When instructed so by the previous step, log on to every node from the original cluster and run the following command on each of them:
cd /appsutil/clone/binperl adcfgclone.pl addracnode <context file>
- Go back to the first node and complete adcfgclone.pl
- If you are adding more than one node to the original cluster, log on to each of the remaining new nodes and run
cd /appsutil/clone/binperl adcfgclone.pl dbTier
- When instructed so by the previous step, log on to every node from the original cluster and run the following command on each of them:
-
| Note: If the cluster manager is not on Linux (ORACM) or the database is version 10g or higher, manually start up the cluster manager on the target systems before running adcfgclone.pl |
- Cloning a Shared File System
You can use Rapid Clone to clone a shared APPL_TOP system. Since all the nodes share a unique APPL_TOP you only need to fully clone one of the source system nodes to its target machine and add more nodes directly sharing the APPL_TOP on the target system. Choose one of the shared APPL_TOP nodes on source system (the rest of this section will refer to it as Node A) and perform the following tasks:- Perform prerequisites
Perform these steps on Node A and and every target nodes. - Clone Oracle Applications 11i
Perform a full clone (Prepare, copy and configure steps) of the Database Tier and Node A (Application tier). - Add the shared file system nodes to the target system
On the target system, follow the instructions for adding a node to a shared APPL_TOP system in document 233428.1adding a node to a shared APPL_TOP system in document 233428.1 on OracleMetalink and add more nodes sharing the target system APPL_TOP to match the source system topology.
- Perform prerequisites
Appendix A: Install JRE 1.3.1 into RDBMS ORACLE_HOME
Windows customers will need to perform the following steps:
- Download JRE 1.3.1 from Sun Microsystems.
- Run the install executable
- When prompted for the location to install jre, click browse and enter the location:
<RDBMS ORACLE_HOME>\jre\1.3.1 - Accept the default installation options.
JRE 1.3.1 will be installed into the <RDBMS ORACLE_HOME>\jre\1.3.1 directory.
Appendix B: Recreating database control files manually in Rapid Clone.
This Appendix documents the steps to allow manual creation of the target database control files within the Rapid Clone process. Examples of when to use this method are for databases on raw partitions or hot backup cloning. Replace section 2.3a (Configure the target system database server) with the following steps:
- Log on to the target system as the ORACLE user
- Configure the <RDBMS ORACLE_HOME>
cd <RDBMS ORACLE_HOME>/appsutil/clone/binperl adcfgclone.pl dbTechStack
- Create the target database control files manually
- Start the target system database in open mode
- Run the library update script against the database
cd <RDBMS ORACLE_HOME>/appsutil/install/<CONTEXT NAME>sqlplus "/ as sysdba" @adupdlib.sql <libext>
where <libext> is “sl” for HP-UX, “so” for any other UNIX platform and not required for Windows.
- Configure the target database (the database must be open)
cd <RDBMS ORACLE_HOME>/appsutil/clone/binperl adcfgclone.pl dbconfig <target context file>
where target context file is:
<RDBMS ORACLE_HOME>/appsutil/<Target CONTEXT_NAME>.xml
| Change Log | |
| Date | Description |
| May 4, 2007 |
|
| March 26, 2007 |
|
| March 25, 2007 |
|
| January 08, 2007 |
|
| December 04, 2006 |
|
| August 16, 2006 |
|
| June 15, 2006 |
|
| May 9, 2006 |
|
| April 25, 2006 |
|
| October 14, 2005 |
|
| June 13, 2005 |
|
| March 09, 2005 |
|
| December 14, 2004 |
|
| December 02, 2004 |
|
| October 19, 2004 |
|
| August 16, 2004 |
|
| July 23, 2004 |
|
| Jan 17, 2003 |
|
November 21, 2009
OPATCH Utility (RDBMS Patching)
Introduction:
This post has been written on request of one of regular visitor of my blog (Altaaf). This post is all about Oracle Patching Utility (OPATCH) and various options that can be used along with Opatch.
We will begin the discussion by knowing what exactly is Opatch?
– OPatch is a java based utility that allow the application and rolling back of interim patches to an Oracle product. The program has sub-commands that may take arguments. The program requires Java(JVM) to be present on the current system.OPatch expects users to have commands such as fuser, jar, ar and make on Unix platforms and jar on Windows platforms to be available in their PATH.
Opatch Details
How to check the Opatch version?
-bash-3.00$ ./opatch version
Invoking OPatch 10.2.0.3.0
OPatch Version: 10.2.0.3.0
OPatch succeeded.
How to know which version is the correct version of Opatch for your RDBMS home?
You can verify whether the Opatch version for your RDBMS release is correct or not using metalink note ID 357221.1.
This note ID gives the copatibilities between OPatch version and RDBMS version.
How to get the latest version of OPatch?
You can download the latest version of OPatch from metalink using following URL.
http://updates.oracle.com/download/6880880.html
In the release dropdown you can select the OPatch release that you want to download based on your RDBMS version. Please read the README.txt before applying the patch.
What is Oracle Database Inventory and where it is located?
Oracle Inventory is the location or the place where all the information about an Oracle Home is stored and maintained. When ever we install an RDBMS Oracle Home, a new inventory gets created. Applying any new patch to Oracle Home will update the invnrtory for that Oracle Home and record the details for the patch applied. This inventory is in the form of XML files.
The location of inventory is defined in a file called oraInst.loc. The path for this file is provided while installing Oracle Home. If we dont supply any path, the is file will be present at central location /etc/oraInst.loc. Also we can have a central inventory if its not used by any other oracle installation. If the central inventory is used by previous Oracle installation we can create local inventory. The content of oraInst.loc file is as shown below.
-bash-3.00$ cd $ORACLE_HOME
-bash-3.00$ cat oraInst.loc
inventory_loc=/slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInventory
inst_group=ems2029
-bash-3.00$
Here “inventory_loc” gives the location of Inventory directory where as inst_group gives the name of the group which is the owner of this inventory.
How to create Local Inventory?
You can create local inventory at any location while installing Oracle Home. You need to use -invPtrLoc variable along with runInstaller command and give the location of oraInst.loc. Otherwise the default path assumed for oraInst.loc is /etc/oraInst.loc.
./runInstaller -invPtrLoc /slot/ems2029/appmgr/apps/tech_st/10.1.2/oraInst.loc
After the installation starts it will ask for location of oraInventory directory and group which should own it. It will make entry of these into oraInst.loc file.
Having know the above information about opatch, now we will move to details about using opatch and various options available.
Opatch help
You can get all the options using opatch -help
-bash-3.00$ ./opatch -help
Invoking OPatch 11.1.0.6.0
Oracle Interim Patch Installer version 11.1.0.6.0
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Usage: opatch [ -help ] [ -r[eport] ] [ command ]
command := apply
lsinventory
prereq
query
rollback
util
version
<global_arguments> := -help Displays the help message for the command.
-report Print the actions without executing.
example:
‘opatch -help’
‘opatch apply -help’
‘opatch lsinventory -help’
‘opatch prereq -help’
‘opatch rollback -help’
‘opatch util -help’
OPatch succeeded.
You can get specific help for any command of opatch using opatch <command> -help. Example opatch apply -help.
Applying single patch using opatch
1. You MUST read the Readme.txt file included in opatch file, look for any prereq. steps/ post installation steps or and DB related changes. Also, make sure that you have the correct opatch version required by this patch.
2.Make sure you have a good backup of database.
3. Make a note of all Invalid objects in the database prior to the patch.
4. Shutdown All the Oracle Processes running from that Oracle Home , including the Listener and Database instance, Management agent etc.
5. You MUST Backup your oracle Home and Inventory
tar cvf – $ORACLE_HOME $ORACLE_HOME/oraInventory | gzip > Backup_Software_Version.tar.gz
6. Unzip the patch in $ORACLE_HOME/patches
If you are applying a single intrim patch to oracle home, then change the location to the directory of that patch and then invoke following command.
Example if I need to apply patch 6972343 to RDBMS Oracle Home
-bash-3.00$ cd 6972343
-bash-3.00$ pwd
/slot/ems2029/oracle/db/tech_st/11.1.0/patches/6972343
-bash-3.00$ ls
etc files README.txt
$ORACLE_HOME/OPatch/opatch apply
If you have created local inventory then you need to give the correct path for local inventory stored in oraInst.loc. If you have updated /etc/oraInst.loc with correct location of your inventory, then above command will work, If not you can give the correct location by giving local oraInst.loc file.
$ORACLE_HOME/OPatch/opatch apply -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Remember that when we are applying patch, patch number is NOT provided as an input to opatch command. So we have to to be in the directory of patch since opatch will pick the patch files from current directory.
Rolling back a patch
In case if a patch did not fix the issue or if you has applied wrong patch to oracle home, you can always rollback the patch using following comamnd.
opatch rollback -id <Patch Number>
Applying bundle patches
Some times if you have to apply bundle patch having many patches, example lets say you want to a bundle patch 6778860 ( 11.1.0.6 BUNDLED PATCH FOR EBS 11I)) containing many other patches to RDBMS home, OPatch provides a facility to apply many patches to RDBMS home using a single comamnd. Following command should be used for applying bundle patches.
Download the patch and extract the same. You will see many directories (one for each patch) inside the main patch directory. Execute following command to apply all patches.
$ORACLE_HOME/OPatch/opatch util NApply -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
NApply -> Will apply all patches to RDBMS home.
You can also use -phBaseDir to point to the directory where bundle patch is installed. So you can run opatch command from any location
$ORACLE_HOME/OPatch/opatch util NApply -phBaseDir /slot/ems2029/oracle/db/tech_st/11.1.0/patches/6778860 -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
You can also apply specific patches using NApply
opatch util napply <patch_location> -id 1,2,3 -skip_subset -skip_duplicate
This will apply patches 1, 2, and 3 which are under < the patch_location> directory. OPatch will skip duplicate patches and subset patches (patches under <patch_location> that are subsets of patches installed in the ORACLE_HOME)
You can see all the options for NApply using following help command.
$ORACLE_HOME/OPatch/opatch util NApply -help
Query the inventory for patches applied
We can query the inventory to check various components installed for database as well as to check various patches applied to database. Use following command to get a minimum information from inventory about patches applied and components installed.
$ORACLE_HOME/OPatch/opatch lsinventory -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Patch 5763576 : applied on Wed May 28 03:20:53 PDT 2008
Created on 6 Feb 2008, 02:26:04 hrs PST8PDT
Bugs fixed:
5763576
If you are using central inventory then -invPtrLoc variable is not required.
You can also get the detailed view of inventory using following command. In case of detail information it gives which are the files that this patch have touched.
$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
Patch 6318357 : applied on Wed May 28 03:33:27 PDT 2008
Created on 4 Dec 2007, 22:02:16 hrs PST8PDT
Bugs fixed:
6318357
Files Touched:
udjvmrm.sql –> ORACLE_HOME/javavm/install/udjvmrm.sql
Patch Location in Inventory:
/slot/ems2029/oracle/db/tech_st/11.1.0/inventory/oneoffs/6318357
Patch Location in Storage area:
/slot/ems2029/oracle/db/tech_st/11.1.0/.patch_storage/6318357_Dec_4_2007_22_02_16
Which options are installed in Oracle Home?
You can check the options installed in RDBMS home using above command. The options installed will be listed at the start of output.
Example: $ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc /slot/ems2029/oracle/db/tech_st/11.1.0/oraInst.loc
The complete output of this command can be seen at this location.
Opatch Log files
Log file for Opatch utility can be found at $ORACLE_HOME/cfgtoollogs/opatch
Advanced Option for OPatch
Here are some of the advanced options of OPatch utility.
UpdateRemoteNodes
It is used to propagate/remove files/directories to/from remote nodes using files under ORACLE_HOME/.patch_storage/<ID>/rac/*.
The directories listed in copy_dirs.txt will be copied to remote nodes.
The files listed in copy_files.txt wil be copied to remote nodes.
The directories listed in remove_dirs.txt will be deleted from remote nodes.
The files listed in remove_files.txt will be deleted from remote nodes.
This is used where RAC setup is present.
Cleanup
It is used to clean up ‘restore.sh, make.txt’ files and ‘rac, scratch, backup’ directories in the ORACLE_HOME/.patch_storage directory. If -ps option is used, then it cleans the above specified areas only for that patch, else for all patches under ORACLE_HOME/.patch_storage. You will be still able to rollback patches after this cleanup.
Example: opatch util cleanup -ps 6121183_Ju _21_2007_04_19_42
CopyListedFiles
It is used to copy all files listed in ORACLE_HOME/.patch_storage/<ID>/rac/copy_files.txt to remote nodes. If -fp option is used, then one can specify the path of the file containing the list of files to be copied. The files mentioned in this file will be copied to the remote nodes.
Example: opatch util copylistedfiles -fp a -remote_nodes ceintcb-a5
This is used where RAC setup is present.
CopyListedFilesTest
It is used to copy a single file to remote nodes. The usage remains the same as CopyListedFiles.
Example: opatch util copylistedfilestest -fp /home/oracle/a -remote_nodes ceintcb-a5
This is used where RAC setup is present.
CopyListedDirs
It is used to recursively copy all directories listed in ORACLE_HOME/.patch_storage/<ID>/rac/copy_dirs.txt to remote nodes. If -dp option is used, then one can specify the path of the file containing the list of directories to be copied. The directories mentioned in this file will be copied to the remote nodes.
This is used where RAC setup is present.
CopyListedDirsTest
It is used to copy a single file to remote nodes. The usage remains the same as CopyListedDirs.
This is used where RAC setup is present.
RemoveListedFiles
It is used to remove files listed in ORACLE_HOME/.patch_storage/<ID>/rac/remove_files.txt on remote nodes. If -fr option is used, then one can specify the path of the file containing the list of files to be removed. The files mentioned in this file will be removed from the remote nodes.
This is used where RAC setup is present.
RemoveListedFilesTest
It is used to remove a single file from remote nodes. The usage remains the same as RemoveListedFiles.
This is used where RAC setup is present.
RemoveListedDirs
It is used to recursively remove directories listed in ORACLE_HOME/.patch_storage/<ID>/rac/remove_dirs.txt from remote nodes. If -dr option is used, then one can specify the path of the file containing the list of directories to be removed. The directories mentioned in this file will be removed from the remote nodes.
This is used where RAC setup is present.
RemoveListedDirsTest
It is used to remove a single directory from remote nodes. The usage remains the same as RemoveListedDirs.
This is used where RAC setup is present.
RunLocalMake
It is used to invoke re-link on the local node. The make commands are stored in ORACLE_HOME/.patch_storage/<ID>/make.txt. You need to use the -ps option to specify the Patch ID with timestamp. A directory by this name will be present under ORACLE_HOME/.patch_storage. The make.txt file present under ORACLE_HOME/.patch_storage/<Patch ID with timestamp>/ will be used to perform the local make operation. This command cannot be run if you have already run Cleanup as it would have removed these make.txt files.
Example: opatch util runlocalmake -ps 6121250_ un_21_2007_04_16_11
RunRemoteMake
It is used to invoke re-link on remote nodes. The make commands are stored in
ORACLE_HOME/.patch_storage/<ID>/rac/makes_cmd.txt. The usage remains the same as RunLocalMake.
This is used where RAC setup is present.
RunAnyCommand
It is used to run any command on remote nodes. The command should be specified using the -cmd option.
Example: opatch util runanycommand -remote_nodes ceintcb-a5 -cmd ls
This is used where RAC setup is present.
LoadXML
It is used to check the validity of an XML file. The -xmlInput option can be used to specify the path of the xml file.
@ Support can use this utility to verify the integrity of XML files contained in the local and central inventory.
Example: opatch util loadxml -xmlInput $ORACLE_HOME/inventory/ContentsXML/comps.xml
Verify
It is used to run the patch verification process to ensure that the patch was applied to the ORACLE_HOME. It uses the defined ORACLE_HOME and the given patch location via -ph, to run the check.
@ Support can use this utility to re-run the OPatch verification stage, if required for patch diagnosis. The patch staging area has to be present or created.
Example: opatch util verify -ph ~/6646853/6121183
Troubleshooting
Some times the inventory get corrupted because of some issues. In that case you need to repair the inventory. Following are the two methods which I know can be used to repair the inventory.
1) Development has released a utility (checkinv) which can be use to repair the inventory if it becomes corrupted for some reason.
Please note that this version of checkinv works only for 9.2 and 10.1 releases of oracle database. This doesn’t work for 10.2 releases of oracle database.
You can download the checkinv utility from Patch 4121946.
To cleanup the components, you should determine the unwanted or dangling components, then specify those using the option “-remcomp”, to cleanup the component list.
The utility detects and asks user’s permission to repair a bad inventory. In case you want to repair the inventory, the utility will first back up the files before any modification.
However, it is better that you backup the inventory before running the tool.
For more details, check metalink note ID 298906.1
2) Creating a new inventory using Oracle Universal Installer (OUI).
Check my older post http://advait.wordpress.com/2008/03/21/creating-oracle-home-inventory-oracle-database-10g/ for the same.
Hope this helps !!
References:
Metalink note ID : 298906.1
Metalink note ID : 554417.1
Metalink note ID : 374092.1
Metalink note ID : 357221.1
Rolling Back Previous Autoconfig Run
In case your autoconfig run has created some issues in your environment and you want to rollback autoconfig run, you can do so by running restore.sh script.
For every autoconfig run, autoconfig will create a directory “MMDDhhmm” under APPL_TOP/admin/TWO_TASK/out. Inside these directories, there will be several files which autoconfig has taken a backup off before making changes. Also there will be a script restore.sh. This script is going to copy these backup files to the original location and this has the effect to rolling back autoconfig run.
(appmgr02) 06190950 – -bash $ pwd
/SLOTS/slot02/appmgr/PQDC2MS1appl/admin/PQDC2MS1/out/06190950
(appmgr02) 06190950 – -bash $ restore.sh
AutoPatch modes, arguements and options
Here are the various options for applying the patch in Oracle apps 11i and R12. ADpatch comes with lots of option that can be used, especially when we are applying the patch in production.
Modes of ADPATCH
If we talk about the mode of applying patch, there are 3 modes
1) Pre-Install Mode
Pre-install mode is used to update AD utilities before an upgrade and to apply family consolidated upgrade packs.
AutoPatch Pre-AutoInstall mode allows you to apply patches when your installation is missing database information and/or filesystem information that AutoPatch requires to run in normal mode.
Examples of when you would run AutoPatch in Pre-AutoInstall mode (and cannot run it in normal mode) include:
- Prior to installing Oracle Applications for the first time
- Prior to upgrading Oracle Applications to the latest release.
- During an upgrade (to apply a bug fix that stopped your upgrade)
Applying patch in pre-install mode performs following tasks:
- Version checking
- File copy actions
- Relink FND and AD executables
- Save patch history information to file system
AutoPatch in pre-install mode will NOT:
- Run SQL of EXEC command
- Generate files
- Read product driver files
- Apply maintenance pack
To apply patch in pre-install mode, run adpatch preinstall=y
2) Test Mode
AutoPatch provides a test mode in which it tells you everything it would have done in applying a patch, but doesn’t actually apply the patch.
To run AutoPatch in Test Mode, you must include ‘apply=no’ on the AutoPatch command line. For example:
$ adpatch apply=no
Instead of performing an action, AutoPatch indicates that it is not performing the action because “Apply=No”. In general, AutoPatch lists each file it would have copied, generated, relinked, or executed. This shows you exactly what actions it would have performed.
AutoPatch test mode works the same as normal mode, with the following exceptions:
- It does not copy any files from your patch directory into your installation area.
- It does not copy any files from your APPL_TOP to JAVA_TOP or OAH_TOP.
- It does not archive any object modules into your product libraries.
- It does not generate any forms or reports.
- It does not relink any executables.
- It does not run any ’sql’ or ‘exec’ commands.
- It does not update the release version in the database.
- It does not update the patch history file.
AutoPatch asks you the same initial questions in test mode as in normal mode. It performs the following actions to determine what it would have done if run in normal mode:
- Reads and validates the patch driver file.
- Reads product file driver files.
- Extracts object modules from your product libraries (so it can perform version checking on the object modules it extracts).
- Performs version checking.
- Looks in the database to determine what ’sql’ and ‘exec’ comands it would have run.
Its a good practice to run the patch in test mode and analyze the things before applying the patch in normal mode.
3) Non-Interactive Mode
Starting in Release 11.5, you can run AutoPatch non-interactively.
Creating a defaults file
Before you can run AutoPatch non-interactively, you must first create an AutoPatch defaults file for your current environment.
Here is a simple way to create an AutoPatch defaults file for your current environment:
1. Specify defaultsfile=<New Defaults File Name> on the AutoPatch command line. The defaults file must be located under $APPL_TOP/admin/<SID>.
For example:
adpatch defaultsfile=$APPL_TOP/admin/testdb1/my_def.txt
2. Run AutoPatch up to the point where it asks you for the directory where your Oracle Applications patch has been unloaded. Then type ‘abort’ at this prompt.
3. Verify that your defaults file exists.
Once you have an AutoPatch defaults file for your current environment, you can run AutoPatch non-interactively.
Applying a single patch driver file non-interactively
Before applying any Oracle Applications patch, either interactively or non-interactively, you should read the README file (usually called readme.txt) supplied with the patch. You should also read the documentation supplied with the patch (if any).
It is possible to apply just a single patch driver file non-interactively using AutoPatch. Here is an example:
Assume the following:
- defaults file is $APPL_TOP/admin/testdb1/def.txt
- Applying copy driver for patch 123456, which is located in directory $APPL_TOP/patch/123456.
- Using three parallel workers
- AutoPatch log file name is cpy123456.log
The AutoPatch command line would be:
adpatch defaultsfile=$APPL_TOP/admin/testdb1/def.txt \
logfile=cpy123456.log \
patchtop=$APPL_TOP/patch/123456 \
driver=c123456.drv \
workers=3 \
interactive=no
If we dont give any of the mode as mentioned above and apply the patch simply using adpatch command then its a normal mode of patch application.
Having seen the modes of patch application, now we will see various arguements for applying patch.
1) defaultsfile
Purpose: This option is used when we are running the patch in non interactive mode. In that case we create defaults file and provide that file as an option for running patch in non-interactive mode.
Default: none. No default file read or written.
2) logfile
Purpose: This is the name of adpatch log file which it will write during patch application.
Default: none. Adpatch prompts for this value.
3) workers
Purpose: Specifies the number of workers to run. This value depends on number of CPU and other factors.
Default: none. Adpatch prompts for this value.
4) patchtop
Purpose: Top-level directory for the current patch. This is the directory after unzipping the patch. This directory will a patch number.
Default: none. Adpatch prompts for this value.
5) driver
Purpose: Name of the patch driver file. This comes with the patch and is present in patch directory.
Default – none. Adpatch prompts for this value.
6) restart
Purpose: To restart an existing session. Only valid when interactive=no is also specified
Default: No
7) localworkers
Purpose: Used in Distributed AD to specify the number of workers to be run on the current machine. If you have multi node instance (example RAC and shared APPL_TOP), then you can utilize this paramter to run the patch parallely in multiple nodes. You can start few workers on node 1, few on node 2 and so on. The way this can be done is that, you can start adpatch on one node with localworker=<some value less then total workers>. Then run adctrl on other node in distributed mode and start some mode workers. This will speed up the process and utilized the resources effectively.
Default: Value specified for workers.
printdebug
Purpose: To display extra debugging information.
Default: No.
Now lets consider some common options that can be used with adpatch options=<value>
1) checkfile
Purpose: To skip running exec, SQL, and exectier commands if they are recorded as already run. Indicates that Autopatch should run the command *only* if a certain file is newer than the version of it that was last run. The idea behind it is to reduce the duration of an Autopatch session by skipping actions that don’t really need to be performed. When used in the right manner, it can dramatically improve Autopatch performance, especially for big patches and/or long running actions.
Default: checkfile (use ‘nocheckfile’ to skip)
2) compiledb
Purpose: To compile invalid objects in the database after running actions in the database driver.
Default: compiledb (use ‘nocompiledb’ to skip)
3) compilejsp
Purpose: To compile out-of-date JSP files, if the patch has copy actions for at least one JSP file.
Default: compilejsp (use’nocompilejsp’ to skip)
4) copyportion
Purpose: To run commands found in a copy driver. This will copy the higher version files from patch to product top.
Default: copyportion (Use ‘nocopyportion’ to skip. Use it only when mentioned in readme of patch)
5) databaseportion
Purpose: To run commands found in a database driver. This portion includes applying the files (like sql, pls etc) to database.
Default: databaseportion (use ‘nodatabaseportion’ to skip. Use it only when mentioned in readme of patch)
6) generateportion
Purpose: To run commands found in a generate driver. This portion will generate new executable files from the copied code of patch. For example if will generate new forms files (fmx) from new .fmb files.
Default: generateportion (use ‘nogenerateporation’ to skip)
7) integrity
Purpose: To perform patch integrity checking. Tells adpatch whether to perform patch integrity checking, which verifies that the version of each file referenced in a copy action matches the version present in the patch.
Default: nointegrity (By default the integrity is not checked)
maintainmrc
Purpose: To maintain the MRC schema after running actions found in the database driver.
Default: maintainmrc (use ‘nomaintainmrc’ to skip)
9) autoconfig
Purpose: Tells adpatch to run Autoconfig after patch installation.
Default: autoconfig (use ‘noautoconfig’ to skip)
10) parallel
Purpose: To run actions that update the database or actions (like SQL) that generate files in parallel (like genform).
Default: parallel (use ‘noparallel’ to skip)
11) prereq
Purpose: Tells adpatch whether to perform prerequisite patch checking prior to running patch driver files that contain actions normally found in the copy driver.
Default: prereq (use ‘noprereq’ to skip)
12) validate
Purpose: To connect to all registered Oracle Applications schemas at the start of the patch. Adpatch validates the passwords for each schema.
Default: novalidate (use ‘validate’ to validate schema passwords)
Following flags can be passed to adpatch
1) hidepw
Purpose: This argument is used to hide the passwords in log files
Default: nohidepw
2) trace
Purpose: Tells the adpatch utility whether to log all database operations to a trace file
Default: notrace
3) logging
Purpose: Tells the adpatch utility whether to create indexes using the logging or nologging mode.
Default: logging
Important tables for ADPATCH
Here are some of the important tables used by and updated by ADPATCH utility.
AD_APPL_TOPS
This table holds the various APPL-TOP’s in the Oracle Applications installation that have ever been patched.
AD_APPLIED_PATCHES
AD_APPLIED_PATCHES holds information about the “distinct” Oracle Applications patches that have been applied. If 2 patches happen to have the same name but are different in content (eg. “merged” patches), then they are considered distinct and this table will therefore hold 2 records.
AD_BUGS
AD_BUGS holds information about the various Oracle Applications bugs whose fixes have been applied (ie. patched) in the Oracle Applications installation.
AD_PATCH_DRIVERS
This table holds information about the patch drivers that comprise a patch.
AD_FILE_VERSIONS
This table holds the various versions of Oracle Applications files (real files, not “pseudo-files”), that have ever been patched or executed in the Oracle Applications installation.
AD_FILES
AD_FILES is the “files repository”. It contains information about the various files that have been patched in the Oracle Applications installation.
Some entries are “pseudo-files” and not real files, (eg. directories) in which case some of the columns are not applicable and would then hold the value “DUMMY”
AD_PATCH_DRIVER_LANGS
NLS patches (or more specifically, NLS patch drivers) pertain to a language or multiple languages. This table holds that language (or multiple languages).
AD_PATCH_DRIVER_MINIPKS
This table holds information about the various Mini Packs contained in a patch (driver)
AD_PATCH_RUN_BUG_ACTIONS holds the various actions present in “applied” bug (fix). If Autopatch determined not to apply a bug (fix), then this table will not hold any records for that “unapplied” bug fix.
AD_PATCH_RUN_BUG_ACTIONS
Even though a patch may have been applied on an Oracle Applications installation, some actions in some of its included bugs (fixes) may not have got executed if the “Autopatch” utility determined that it was not necessary to execute those actions. In such cases, EXECUTED_FLAG is set to N.
AD_PATCH_RUN_BUGS
This table holds information about the bugs fixed in a specific run of Autopatch.
AD_PATCH_RUN_BUGS holds information about the various bugs fixed in a specific run of Autopatch.
Even though a patch may have been applied on an Oracle Applications installation, some bugs (fixes) contained in it may not get applied due to some reason. In such cases, the REASON_NOT_APPLIED column holds the reason.
AD_PATCH_RUNS
AD_PATCH_RUNS holds information about the various invocations of Autopatch for applying Oracle Applications patches to a specific release of an Oracle Applications installation.
If multiple drivers are run in one invocation of Autopatch, they result in multiple records in this table. These multiple records will all have the same SESSION_ID (because they arose from one Autopatch invocation), but different TASK_NUMBER’s. The TASK_NUMBER’s in this case will be numbered sequentially as 1, 2, 3, etc.
Note that when the database driver of a Maintenance Pack is applied, it bumps up the release version by creating a new record in AD_RELEASES, which is then pointed to by the UPDATED_TO_RELEASE_ID column of the old record.
AD_RELEASES
AD_RELEASES holds the various Oracle Applications releases that an installation of Oracle Applications has gone through in its entire life cycle.
It should be noted that START_DATE_ACTIVE, END_DATE_ACTIVE and BASE_RELEASE_FLAG are loosely-maintained informational columns and are not accurately maintained, and therefore should not be relied upon heavily.
AD_PATCH_COMMON_ACTIONS
This table holds distinct information about the various actions that are (often repeatedly) performed by Autopatch as part of applying patches.
Hope this helps !!
References:
Metalink ETRM DIRECT ACCESS DOCUMENT 150230.1
No Active Responsibilities available for Apps user
Problem Statement : Recently I encountered a problem in Oracle Apps 11i (11.5.9). When a user login into the application he/she gets error “There are no active responsibilities available for this user”and user is not able to see any responsibility in the home page.
The problem is same even for sysadmin user. Now the challenge is that, if the system administrator is also not able to see any responsibility then its very difficult to administer other users facing same problem. So here is the solution that I found out as per metalink note ID 316959.1
Solution :
Part 1: Verification
Execute following queries for verification as per metalink note ID 335487.1
1) Please check if table FND_USER_RESP_GROUPS was backed up to table FND_USER_RESP_GROUPS_OLD in the APPLSYS schema, and verify that there is a SYNONYM FND_USER_RESP_GROUPS_OLD in the APPS schema.
SELECT OWNER, OBJECT_NAME, OBJECT_TYPE
FROM ALL_OBJECTS
WHERE OBJECT_NAME LIKE ’FND_USER_RESP_GROUPS_OLD’
AND OBJECT_TYPE IN (‘VIEW’,’TABLE’, ‘SYNONYM’);
OWNER OBJECT_NAME OBJECT_TYPE
—————————— —————————— ——————
APPLSYS FND_USER_RESP_GROUPS_OLD TABLE
APPS FND_USER_RESP_GROUPS_OLD SYNONYM
2) Check if object FND_USER_RESP_GROUPS is a view or a table
SQL> SELECT OWNER, OBJECT_NAME, OBJECT_TYPE
FROM ALL_OBJECTS WHERE OBJECT_NAME LIKE ‘FND_USER_RESP_GROUPS’; 2
OWNER OBJECT_NAME OBJECT_TYPE
—————————— —————————— ——————
APPS FND_USER_RESP_GROUPS VIEW
APPS_MRC FND_USER_RESP_GROUPS SYNONYM
RTREADONLY FND_USER_RESP_GROUPS SYNONYM
FND_USER_RESP_GROUPS should be a view in APPS schema.
If FND_USER_RESP_GROUPS is of type TABLE in the APPLSYS schema please apply solution from step 3 from metalink note ID 335487.1
Else execute following steps from metalink note ID 316959.1
Part 2: Fix
Run following SQLs
1)
SELECT *
FROM Fnd_Responsibility_vl
WHERE Application_Id = 1
AND Responsibility_Name = ‘System Administrator’
AND Start_Date <= Sysdate
AND ( End_Date is NULL OR End_Date > Sysdate );
2)
SELECT count(*)
FROM Fnd_User_Resp_Groups;
3)
Back up the wf_role_hierarchies table into a new table you create.
CREATE TABLE wf_role_hierarchies_copy AS
SELECT * FROM wf_role_hierarchies;
Delete the entries in that table (2 rows exist)
TRUNCATE TABLE applsys.wf_role_hierarchies;
Run affurgol.sql FORCE
SQL> @$FND_TOP/patch/115/sql/affurgol.sql FORCE
Then replace those entries back into wf_role_hierarchies table
SQL> INSERT INTO wf_role_hierarchies
SELECT * FROM wf_role_hierarchies_copy;
Bounce Apache and try to login as sysadmin. You should be able to see the correct responsibilities.
Hope this helps !!
How to Change Apps Password in 11i, if you forget ?
We need to change apps password manually, if you forgot and can’t check it in wdbsvr.app at $IAS_ORACLE_HOME/Apache/modplsql/cfg .
Please remember that the APPLSYS and APPS passwords always
have to be the same. Always change both at the same time. When changing these
passwords, it is important to change the APPLSYS password first and the APPS later.
please back up the FND_ORACLE_ID and FND_USER tables before beginning.
1. Have all users log out of applications.
2. Shutdown the concurrent managers. (You can’t shutdown using adcmctl.sh if you don’t know apps password so use frontend)
3. Log in to applications as System Administrator.
4. Navigate to Security> Oracle> Register
5. Query up all available Oracle Ids.
(NOTE: do not log out of this session of Applications until you have verified
that all the following steps have been completed successfully).
6. At the same time, login to SQL*PLUS as the SYSTEM user.
7. In the applications session, enter the new password for APPLSYS. Re-enter (Same time do it in SQLPLUS ,after finishing Application part))
the same password when asked to re-enter the password to confirm.
8. Save the change.
Note: At this point of the procedure you will see a “Caution” dialog box which states the following:
“You are changing the APPLSYS password. Doing so will affect the whole system”.
NOTE: The first character of the APPLSYS password MUST NOT BE a numeric.
Use only alpha characters for the first character in the APPLSYS password.
all APPS schema passwords to match the APPLSYS password.
9. In the same applications session, change the APPS password.
Note: Re-query the form (query – run) every time after changing the APPS
password. If it is not re-queried and the APPS password is changed again, it is
impossible to continue.
10. In the SQL*Plus session, issue the following statements to change the
passwords in the database, where ‘XXX’ is the password assigned to that
user in the previous steps:
sql>ALTER USER APPLSYS IDENTIFIED BY XXX;
sql>ALTER USER APPS IDENTIFIED BY XXX;
“Remember don’t log out from the application yet”
11. Open a NEW session in applications, WITHOUT CLOSING THE PREVIOUS SESSION,
and log in.
If log in is successful, the change was successful. Otherwise, repeat steps 5
onward, ensuring the same password is used for both APPLSYS and APPS, in both
applications and SQL*Plus.
Followed the Metalink Doc Note:160337.1
But no need to change the password for APPLSYSPUB and in metalink note they did not mention about autoconfig..
The most important thing … Please run autoconfig. so that change will effect the entire system.
How to generate FRD trace
The steps I have followed :-
1. Login as oracle application user
2. Go to $FND_TOP/secure
3. java oracle.apps.fnd.security.AdminAppServer apps/ \AUTHENTICATION ON DBC=
Please check the below example :-
4. java oracle.apps.fnd.security.AdminAppServer apps/ffdev21 \AUTHENTICATION ON DBC=ffus.com_ffus.dbc
Output will be :-
AUTHENTICATION ON executed successfully – ffus.com_ffus.dbc
5. In the command prompt echo $FORMS60_TRACE_PATH
It will give you the trace path. Make sure the path is set.
6. Open internet explorer
Type the url below :-
http://:/dev60cgi/f60cgi/?&record=collect&log=$FORMS60_TRACE_PATH/
even you can change =$FORMS60_TRACE_PATH and can have your own path but make sure that path has got read and write permission .It is advisable to have default path.
Example is below :-
http://ffus.com:8000/dev60cgi/f60cgi/?&record=collect&log=$FORMS60_TRACE_PATH/faoracle.frd
Now you can generate FRD trace depend upon your situation
It will generate FRD trace file in your $FORMS60_TRACE_PATH directory with the name supplied by you in URL.
After finishing the the entire task make sure that you disable the trace :-
The steps are as follows:-
Note :- It has got security issues ,so make it disable.
1.Login as oracle application user
2.Go to $FND_TOP/secure
3. java oracle.apps.fnd.security.AdminAppServer apps/ \AUTHENTICATION OFF DBC=
4. java oracle.apps.fnd.security.AdminAppServer apps/ffdev21 \AUTHENTICATION OFF DBC=ffus.com_ffus.dbc
Output will be :-
AUTHENTICATION OFF executed successfully – ffus.com_ffus.dbc
Alternative Steps:
Backup and open $APPL_TOP/admin/_.xml context file
2. Update the context variable:
s_appserverid_authentication
By default in 11.5.10, this is set to SECURE.
In previous 11i versions, this was set to OFF.
For debug purposes, you can use ON or OFF
Make it ON
3. Run Autoconfig to instantiate the change.
You should now be able to access forms directly again using the f60cgi call.
4. After you have finished your Forms debugging, please reset
s_appserverid_authentication to SECURE and re-run Autoconfig
Jcprasad's Blog 