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.

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.

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).

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.

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.

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.

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.

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).

glibc Requirements

The following table lists the required minimum glibc versions (to determine this, enter: $ rpm -q glibc).

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:

1. 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>

1. Verify that the /etc/sysconfig/network file is formatted as follows:

5.  HOSTNAME=<node_name>.<domain_name>

1. If the /etc/sysconfig/networking/profiles/default/network file exists, remove it.
2. If you changed any files in the previous steps, restart the system.

For SUSE Linux Enterprise Server 8, 9 and 10:

1. 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>

1. 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.

1. 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

1. 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

1. 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.

1. Unset the NLS_LANG environment variable, if it is defined prior to installation.
2. For Red Hat Enterprise Linux 3, apply the OS library patch 3006854 (downloadable from OracleMetaLink).
3. 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.
   1. Download the patch 6365595 from OracleMetalink.
   2. Follow the Oracle Applications Installation guide and set up the stage area.
   3. 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.
   4. 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
   5. 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
   6. 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
   7. 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

1. 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.

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.

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.

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.

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.

1. Open the Windows Explorer
2. Navigate to the system root directory (default is C:\winnt\system32).
3. Right-click msxm13.dll. Select Properties. them click Version.
4. 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:

http://www.microsoft.com/downloads/ThankYou.aspx?fami lyId=b432cd45-b7ed-4c32-a443-ec56f10ee175&displayLang=en

1. 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.

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.

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

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).

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).

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 Release 11i
with Rapid Clone

• Creating a copy of the production system for testing updates.
• Migrating an existing system to new hardware.
• Creating a stage area to reduce patching downtime.

This document describes the process of cloning an Oracle Applications Release 11i system. The most current version of this note is document 230672.1 on OracleMetaLink. A FAQ is also available in document 230672.1 on OracleMetaLink. A FAQ is also available in document 216664.1 on OracleMetaLink.document 216664.1 on OracleMetaLink.

• 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

Section 1: Prerequisites

Before cloning, prepare the source system by applying patches and running AutoConfig.

1. 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.

1. 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.
2. Windows users only:
   Apply patch 2237858 to enable long file names support.
3. 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.
4. 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 :
   • 3453499 (11i.ADX.F)
   • 5225940 (Post ADX.F Fixes)
   • 5972212 (For SLES 10)
5. Setup Rapid Clone on the Applications Tier

1. 1. 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).

1. All users must run AutoConfig on the Applications Tier (see section 5: Maintaining System Configuration Maintaining System Configuration in document 165195.1 on OracleMetaLink).

1. 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).

1. 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:

1. Prepare the Source System
   Execute the following commands to prepare the source system for cloning.
   1. 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
   2. 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
2. 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.
   1. 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>
   2. 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

1. 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)
   1. 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
   2. 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

Section 3: Finishing Tasks

This section lists tasks that may be necessary depending on your implementation and the intended use of the cloned system.

1. 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.
2. Update printer settings
   If the new cloned system needs to utilize different printers, update the target system with the new printer settings now.
3. 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.

1. 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 of s_applcsf in the contextfile and run AutoConfig.
2. 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.
3. 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.

1. 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:

1. 1. Prepare the Source System
   2. 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.
   3. 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>.xml
      • perl adcfgclone.pl appsTier <Appltop target context file>
        where appltop context file is:
        <APPL_TOP>/admin/<Target CONTEXT_NAME>.xml
   4. Finishing Tasks
2. 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:

1. • 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.

1. 1. Perform prerequisites
      Perform these steps on all source and target nodes.
   2. 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.
   3. Finishing Tasks

1. 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.

1. • 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.

1. 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

1. 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.
2. 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:

1. 1. 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
   2. 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.

1. 1. 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.
   2. Configure the Target System
      • Log on to any ORACLE_HOME in the target cluster and run
        • adcfgclone.pl dbTier

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.

1. 1. • 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>

1. 1. 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.

1. 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:
   1. 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).
   2. Copy the master ORACLE_HOME filesystem to the new node(s).
   3. 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/bin
        • perl adcfgclone.pl dbTier

1. 1. • 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/bin
        • perl 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/bin
        • perl adcfgclone.pl dbTier

1. 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:
   1. Perform prerequisites
      Perform these steps on Node A and and every target nodes.
   2. Clone Oracle Applications 11i
      Perform a full clone (Prepare, copy and configure steps) of the Database Tier and Node A (Application tier).
   3. 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.

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/bin
  • perl 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/bin
  • perl adcfgclone.pl dbconfig <target context file>
    where target context file is:

<RDBMS ORACLE_HOME>/appsutil/<Target CONTEXT_NAME&gt.xml

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

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

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

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.

or Refer this Link

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

or Refer this link

1. what is the utility to change the password of a dba schema in oracle apps? Ans: FNDCPASS
2. what are mandatory users in oracle apps?
Ans: applsys,applsyspub,apps
3. What simplay a oracle Architechture?
Ans: Desktop Tier, Application Tier, Database Tier

5. What are the components in the Application Tier?
Ans: Apache(http)
Jserver(jre)
Forms Server(f60srv)
Metric Server(d2ls)
Metric Client(d2lc)
Report Server(rwm60)
Concurrent Server(FNDLIBR)
Discoverer

6.What are main file systems in Oracle Apps?
Ans: APPL_TOP, COMMON_TOP,
DB_TOP,ORA_TOP

7. What are there in Desktop Tier?
Ans: Internet Browser, JInitiator

8. What is the location of JInitiator in the Desktop Tier?
Ans: c:\program files\oracle\Jinitiator

9. What is the location of client cache?
Ans: c:\documents and settngs\user\oracle jar Cache

10. What is the location of Server cache?
Ans: $COMMON_TOP/_pages
11. Which package will be used for the user validation by plsql agent?
Ans: oraclemypage
12. What are adadmin utilities? and Its location?
$AD_TOP/bin
Ans: 1.adadmin
2.adpatch
3.adsplice
4.adident
5.adrelink
6.adlicmgr
13.What are the location of JaVA Files?
Ans: JAVA_TOP and all PRODUCT_TOP/Java/Jar
14. What is the name of the xml file of Apps and its location?
Ans: Context Name.xml and $APPL_TOP/admin
15. what is the location of Apps environment file? and its name?
Ans: contextname.env and $APPL_TOP
16. In how many way Jar files are generated?
Ans: Normal and Force
17. Once Jar files are generated what files get effected?
Ans: All Product_top/java/jar files and Two files in JAVA_TOP they are appsborg.zip
appsborg2.zip
18. How do you see the files in zip file?
Ans: unzip -v
19.How do you generate jar files?
Ans: Using adadmin and option 5
20. How do you start the apps services?
Ans: $COMMON_TOP\admin\scripts\Contextname\adstrtal.sh apps/appspwd
21. What is the executable to generate jar files?
Ans: adjava
22. How do you relink a executable of a product
Ans: by relinking option in adadmin or adrelink
23. How do you relink AD product executable? and usage?
Ans: adrelink.sh and adrelink.sh force=y “ad adsplice”
24.When do you relinking?
Ans: 1. when you miss a executable file
2. When there is a problem with any executable file
3. When any product executable get currupted
25. What is DAD?
Ans: It is a file which stores apps passwords in hard coded format. i.e wdbsvr
26.How do you relink OS files and libraries?
Ans: using make command
27.What is compile scheman option in adadmin?
Ans: This option is used to compile/resolve the invalid objects
28. Where do you get the info about invalid objects?
Ans: from dba_objects where status=invalid

29.How do you compile an obect ?
Ans: alter object_ type objet _name compile. Eg: alter table fnd_nodes compile
30.How do you see the errors of a table or view?
Ans: select text from dba_errors where name=’emp_view’
31. How do you see the errors in the db?
Ans: show error
32. How do you compile a schema?
Ans: using utlrp.sql (location is ?/rdbms/admin/) or
going adadmin, compile schema option
33. How do you know how many invalid objects are in specific schema?
Ans: select count(*) from dba_objects where status=’INVALID’ group by owner;
34. How do you know the package version?
Ans: select text from dba_source where name=’package name’ and type=’PACKAGE BODY’ and rownum<10>/rdbms/admin)
41. How do you load java class to databae?
Ans: loadjava
42. What are restart files? and its location?
Ans: These files contains the previouse session info about adadmin.. location is $APPL_TOP\admin\sid\restart\*.rf9
43.How do you validate apps schema?
Ans: To validate synonyms, missing sysnonyms and all grant. You can do it in adadmin. after validating it iwll produce
a report in the location $APPL_TOP\admin\sid\out\*.out
44. How do you enable maintainance mode?
Ans: using adadmin or running a script called “adsetmmd.sql ENABLE/DISABLE” (AD_TOP/patch/115/sql)
45.What is APPS_MRC Schema?
Ans: It is used for multi language support. To synchronize APPs schema and APPS_MRC
46. How to see the version of a script or form or report or etc?
Ans: grep Header adsetmmd.sql or adident Header adsetmmd.sql
strings -a GLXSTEA.fmx grep Header or adident Header GLXSTEA.fmx
47.What is the location of adadmin log?
Ans: $APPL_TOP\admin\sid\log
48. What are the oracle homes in Apps?
Ans: 8.0.6ORACLE_HOME(Dev 6i products) and IAS_ORACLE_HOME (Apache)
49. How do you configure you ipaddress at client side? and server side?
Ans: c:\windows\system32\drivers\etc\hosts and \etc\host
50. What is the location of Datbase server related scripts?
Ans: $ORACLE_HOME\appsutil\scripts\contextname
51. what is the utility to clean the concurrent manager?
Ans: @cmclean.sql ( You have download from metalink)
52. How do you stage the 11.5.10 Apps software?
Ans: using adautostg.pl
53. What is the location of the source files of forms?
Ans: AU_TOP/forms/US/
54. What is the executable to generate forms?
Ans: f60gen