EBS Installation

This EBS Installation document explains the basic steps for installing EBS on a Linux machine using Rapid Installer, but without the Vision
Database. It covers steps necessary to install the 12.1.1 release, upgrade it to 12.1.3, and then apply the Oracle Product Hub (OPH) 12.1.3 Rollup
patch. This document provides information on the following topics:

1. Scope

2. Preparing the Environment

3. Installation

4. Post Installation Steps

5. Upgrade to 12.1.3

6. Steps for Applying OPH 12.1.3.1 PIM Rollup Patch1

7. Install the Oracle E-Business Suite Integrated SOA Gateway (ISG)

8. Troubleshooting Tips

9. References

Top

1. Scope

OPH is a module in the Oracle E-Business Suite (EBS). EBS installation is a pre-requisite for OPH. The information in this EBS Installation topic is
based on the Oracle E-Business Suite Installation Guide: Using Rapid Install (also known as the Rapid Install guide) and is intended to ease the
installation of EBS for Product Hub for Communications (PH4C). This topic only explains the installation of EBS using the rapid install tool without
Vision Database. This topic is not intended as a replacement for the Rapid Install guide. For further clarification, refer to the Rapid Install Guide.
EBS Rapid Install offers two options for a new installation:

Standard installation - involves creating a new system using system-specific configuration parameters.

Express installation - Rapid Install supplies default values for many parameters, requiring only a few to be supplied by the user performing
the install.

This document explains how to use Rapid Install in Express Installation mode.

Top

2. Preparing the Environment

This section is based on the installation procedure for a Linux machine with the specifications listed below:

1 of 31
System Specifications Used

Operating System Enterprise Linux x86 64-bit

Release 4
Disk space 195 GB
Processor Genuine Intel® Xeon® CPU X5675 at 3.07 GHz
Kernel 2.6.9-103.0.0.0.1.ELxenU

Note: Most of the steps are similar for EBS installation on other operating systems. Refer to the Oracle E-Business Suite Installation Guide:
Using Rapid Install for any operating system (OS) specific instructions.

1. Space Requirement

The total space required for a standard system (not including the Stage Area) is 85 GB for a fresh install with a production database.

For more information about space requirements, see Disk Space Requirements, Oracle E-Business Suite Installation Guide: Using Rapid Install.

2. Download EBS 12.1.1

You can download the EBS software from this URL (https://edelivery.oracle.com). Select the appropriate OS (for example, for Linux X86 64-bit OS,
choose Linux X86-64) as the platform and download the appropriate EBS software release (12.1.1). Download products starting from product code
B53824 to product code V15691. Unzip all the content to create stage directories.

For more information, see <Document 1527786.1> and <Document 406138.1> .

3. Verify the Packages

Before running Rapid Install, read the relevant Oracle E-Business Suite platform-specific Installation and Update notes, available on My Oracle
Support (MOS).

For Linux X86 64-bit platforms, refer to <Document 761566.1>. For information about other platforms, refer to Review Associated Documentation,
Oracle E-Business Suite Installation Guide: Using Rapid Install.

Note: All packages listed in <Document 761566.1> should exist in the environment where EBS needs to be installed. Unavailable packages
needs be downloaded and installed.

4. Set Display for the Machine

2 of 31
Set the environment variable DISPLAY to an active and authorized display. If nedit is launched successfully, there is no need to set the
environment variable DISPLAY. Refer to Troubleshooting Tips if you encounter an error while launching nedit.

Use the following command to determine whether the DISPLAY variable is set or not.
$ echo $DISPLAY
localhost:10.0

5. Networking - Hosts Name Settings

The /etc/hosts file must contain a fully qualified name for the server:

<IP-address> <fully-qualified-machine-name> <hostname>

You must configure the host to resolve hostnames to the loopback IP address by modifying the /etc/hosts file to contain the following entries:
$ cat /etc/hosts
# HEADER: This file was autogenerated at Tue Jun 11 11:56:55 +0000 2013
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
127.0.0.1 localhost.localdomain localhost
<IP Address> <fully-qualified-machine-name> < hostname >

Ping the host to verify it is working.

$ ping < hostname >
PING < hostname > (<IP Address>) 56(84) bytes of data.
64 bytes from < hostname > (<IP Address>): icmp_seq=0 ttl=64 time=0.012 ms
64 bytes from < hostname > (<IP Address>): icmp_seq=1 ttl=64 time=0.020 ms

For more information, see Networking, Oracle E-Business Suite Installation Guide: Using Rapid Install.

6. Verify /etc/sysconfig/network

Verify that the host name is present in the network file.

$ cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=<hostname>
GATEWAY=<gateway>
NISDOMAIN=<domain name>

7. Verify Kernel Settings

Before running Rapid Install, read the relevant Oracle E-Business Suite platform-specific Installation and Update notes, available on My Oracle
Support. For Linux X86 64-bit platforms, refer to <Document 761566.1>. For other platforms, refer to Review Associated Documentation, Oracle
E-Business Suite Installation Guide: Using Rapid Install.

Use the following command to determine the kernel values.

Usage:
/sbin/sysctl -a | grep <param-name>

3 of 31
Example:
$ /sbin/sysctl -a | grep kernel.shmmax

Output:
kernel.shmmax = 1073741824

In a similar manner, verify the remaining kernel parameter values. Enter the missing parameter values in the configuration file (/etc/sysctl.conf).
After modifying the configuration file (/etc/sysctl.conf) with new values, run the following command to reflect those values.
$ /sbin/sysctl –p

Note: If the current value for any parameter is higher than the value listed in the respective MOS Doc ID, then do not change the value of
that parameter.

8. The Resolver - DNS Parameters

DNS resolver parameters (timeout and attempts) are set by default to low values. Change them to the following values:
timeout:5
attempts:15
$ cat /etc/resolv.conf
#
# Optional values recommended by GIT
#
options timeout:5
options attempts:15

9. Limiting User Processes

To limit user processes, open the /etc/security/limits.conf file and change the existing values for “hard” and “soft” parameters as follows.
* hard    nofile          65535
* soft    nofile          4096
* hard    nproc           16384
* soft    nproc           2047

Restart the system after making changes.

Note: If the current value for any parameter is higher than the value listed in this document, then do not change the value of that parameter.

10. Create Operating System Accounts

Before running Rapid Install, you must create the operating system accounts that will be used in the installation of the database node and
Applications node file systems.

Single-user installation: one user used for the two file systems (Application and Database).
4 of 31
 Multi-user installations: one user per file system.

This document assumes a single user for installation in Express mode.

The default name for the Oracle user is ora<SID>. For example, for a production (PROD) environment, the default Oracle OS username might be
oraprod.

Use the following command to create a Linux user.

useradd -m -g dba oraprod -d /scratch/oraprod

For more information, see Create Operating System Accounts, Oracle E-Business Suite Installation Guide: Using Rapid Install.

11. Create Directories

Inventory Directory - oraInst.loc

oraInst.loc must be located in /etc (for Linux and IBM AIX) or /var/opt/oracle (for Solaris, HP-UX PA RISC, and HP-UX Itanium).

oraInst.loc must point to a valid central inventory location.

The central inventory location must be writable by the owner of the Oracle files and the application files.

If oraInst.loc does not exist, create it in the proper directory. The contents should look like this:

inventory_loc=/d01/oracle/oraInventory

For more information, refer to Verify oraInst.loc, <Document 798258.1>.

Installation Directories

Create a top-level installation directory and provide full access to the user and group. The same directory path is used during installation using
Rapid Install. Use the following commands to create a top-level installation directory.

mkdir -p /d01/oracle/<SID> (top-level installation directory or base directory)

$ mkdir -p /d01/oracle/PROD

mkdir -p /d01/oracle/<SID>/inst
$ mkdir -p /d01/oracle/PROD/inst

chown -R <username>:<group name> /d01

$ chown -R oraprod:dba /d01

$ chmod -R 775 /d01

12. Unset Env

Do not set the $ENV environment variable before starting the installation, because it can alter variables that are set by the Oracle installation
scripts. For more information, see Create Operating System Accounts, Oracle E-Business Suite Installation Guide: Using Rapid Install.

Note: The steps you have completed so far correspond to the section “Before You Install” in the Oracle E-Business Suite Installation Guide:
Using Rapid Install.
5 of 31
Top

3. Installation

This section summarizes the information provided in the “Performing an Installation” chapter of the Oracle E-Business Suite Installation Guide:
Using Rapid Install. Rapid Install offers two options for a new installation: a standard installation, which involves creating a new system using
system-specific configuration parameters, and an Express installation, where Rapid Install supplies default values for many parameters, requiring
only a few to be supplied by the user carrying out the install. This document focuses on Express Installation Mode. For more information, see
Express Installation, Oracle E-Business Suite Installation Guide: Using Rapid Install.

Login with the user (oraprod) created in the previous step.

Go to the Stage directory (the directory where the EBS software dump is present):
$ cd <stage directory path>
$ cd startCD/Disk1/rapidwiz/
$ ./rapidwiz

A java based Installer widget will appear, as shown below:

Click Next.

6 of 31
Select the Express Install option (this option enables the Installer to set most of the configuration parameters for you).

Click Next.

7 of 31
In the above window, provide appropriate values as explained below:

Database Type – Select Fresh Database from the list of values.

Database SID – Accept the default SID for the production database,PROD.

Domain – <domain name>. The complete host name will be formed from <Node_name>.<Domain_name>.

Base directory - Provide the base directory where you want to install. (Provide the top-level installation directory created in the previous
step).

Instance directory - this field is populated automatically.

Port Pool – Accept the default value.

After providing the appropriate values in the wizard window above, click Next.

The following window provides the status of the system checks performed. For more information about pre-install checks, see Pre-Install Checks,
Oracle E-Business Suite Installation Guide: Using Rapid Install.

8 of 31
If a pre-install test has an exclamation mark (!) or an X icon beside it, click on it to see the details stored during the check process. For example, if
you see an exclamation mark beside the File Space test, clicking on it may display a window such as this:

Resolve any issues and then click OK to return to the Pre-install Checks window. If you decide to continue the installation without fixing the flagged
issues, Rapid Install displays the following warning when you click Next.

9 of 31
Click Yes to continue or No to stop the installation. If you click No, you must go back to the appropriate window and correct the incorrect or
incompatible parameter. Once you resolve the issues (if any) and click Next, the following window appears.

Click Next to display the Alert window below:

10 of 31
Click Yes to start the installation process and display the progress window below.

During an installation, Rapid Install displays a main progress bar and an individual progress bar. The main progress bar reports the completion
percentage of the installation as a whole. The individual progress bar reports the progress of each individual step. The installation is not complete
until all of the progress bars disappear from your screen.

After the installation is complete, Rapid Install automatically validates the installed Oracle E-Business Suite environment. Tests include database
availability, correctly-configured environment files, and functioning listeners. For more information, see Post-Install Review, Oracle E-Business
11 of 31
Suite Installation Guide: Using Rapid Install.

If there is an (! or X) icon, click it to see the details. If any of the checks fail, refer to the Rapid Install log files to determine the reason and resolve
each problem before continuing. When the errors are fixed, click Retry to perform the post-install validation again.

Click Next if there are no errors. Rapid Install informs you of the components that it installed on the Finish window as shown below.

12 of 31
If you wish to review the Post-install Checks, click Back. If you want to log on to Oracle E-Business Suite now, click Connect to Oracle
Applications Release 12.1.1 to access the Oracle E-Business Suite Login page. Otherwise, click Finish to complete the Rapid Install session.

From the Oracle E-Business Suite Login page, you can access the E-Business Suite Home Page, which provides a single point of access to
HTML-based applications, forms-based applications, and Business Intelligence applications. You access the Oracle E-Business Suite Login page
from the following URL:
Example
http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLogin

Enter a suitable username and password. Use the following default credentials to log in as system administrator:

User: SYSADMIN (this is a privileged account that has the System Administrator responsibility)
Password: SYSADMIN

For more information, see Log in to Oracle E-Business Suite, Oracle E-Business Suite Installation Guide: Using Rapid Install.

After your credentials have been validated, the Oracle E-Business Suite Home Page appears. From this page, you can access responsibilities for
any of the individual Oracle E-Business Suite products your organization has licensed.

13 of 31
Top

4. Post Installation Steps

Once the installation is complete, there are some final steps that are required. You need to enable your license for Product Hub for
Communications. Rapid Install installs the file system and database files for all products, regardless of their licensed status. Only license-enabled
products are accessible.

Note: For more information, see License Manager, Oracle E-Business Suite System Administrator's Guide - Maintenance.

1. Enable Licensing (according to your Oracle licensing agreement)

Caution: Users must purchase a license before proceeding with the following steps.

Perform the following steps to enable your license for a product (such as Product Hub for Communications).

14 of 31
Navigation: System Administrator > Oracle Applications Manager > License Manager.

Click License Manager to open the License Manager page.

Click Products

15 of 31
Select the option License Component Application to enable licenses for individual products. Click Continue.

Enable the four products shown above.

Click Submit to enable the licenses for the products.

16 of 31
Click OK .

2. Set BNE Profiles

OPH uses WebADI for Excel Import and Export features. Set WebADI profile options to the site level according to <Document 549758.1>. Source
the application environment file to set the value for variable $BNE_TOP, $COMMON_TOP.

1. Login to the instance and go to the directory where the .env file exists.
      $ cd < base directory path>/apps/apps_st/appl/
2. Run the application environment file.
    $ . ./APPS<SID>_<hostname>.env

3. Check if the values are set for environment variables $BNE_TOP, $COMMON_TOP and $OA_HTML.
    $ echo $BNE_TOP
   <base directory path>/apps/apps_st/appl/bne/12.0.0

4. Check for the existence of the following directories under $BNE_TOP, $COMMON_TOP and $OA_HTML. Create them if they do not exist.

$BNE_TOP/upload

$BNE_TOP/upload/import

$COMMON_TOP/webapps/oacore/html/cabo/

$OA_HTML/cabo

5. Change the privileges to 777 for the following directories.

$BNE_TOP/log/

$BNE_TOP/upload/

$BNE_TOP/upload/import

$COMMON_TOP/webapps/oacore/html/cabo/

$OA_HTML/cabo

6. Set values for each profile shown below.

17 of 31
 BNE_SERVER_LOG_PATH                        $BNE_TOP/log

BNE_SERVER_LOG_LEVEL                      Trace

BNE_SERVLET_PATH                                 /OA_HTML/

BNE_UIX_BASE_PATH                                /OA_HTML/cabo

BNE_UIX_PHYSICAL_DIRECTORY           $OA_HTML/cabo

BNE_UPLOAD_IMPORT_DIRECTORY     $BNE_TOP/upload/import

BNE_UPLOAD_STAGING_DIRECTORY $BNE_TOP/upload

BNE_UPLOAD_TEXT_DIRECTORY          $BNE_TOP/upload

Top

5. Upgrade to 12.1.3

For information on upgrading to the12.1.3 release, refer to <Document 1080973.1>.

This section covers upgrading the environment to 12.1.3 after you have installed 12.1.1 by following the steps described previously in this
document. To upgrade to release 12.1.3, you will apply a few patches. This section explains which patches to apply and how to apply them in
detail. For more information, refer to <Document 1080973.1>.

1. List of Patches Required for a 12.1.3 Upgrade

Patch 9239089 (R12.AD.B.delta.3)

Patch 9239090

Patch 9239095

Patch 9817770 (9817770:R12.ATG_PF.B)

Patch 9966055 (9966055:R12.FND.B)

Create a directory in which to download the above listed patches, then unzip them.

2. Install patches

1. Set the application environment.

$ cd <base directory>/apps/apps_st/appl/
$ . ./APPS<SID>_<hostname>.env

2. Stop all application processes.

$ $INST_TOP/admin/scripts/ adstpall.sh       apps/apps

3. Set the environment to RDBMS oracle_home.

18 of 31
 $ cd <base directory>/db/tech_st/11.1.0
$ . ./ <SID>_<hostname>.env

Determine whether the environment variables $ORACL_HOME and $ORACLE_SID are set or not.

4. Shut down the database.

If you set the environment variables ORACLE_HOME and ORACLE_SID and the user you are using on the Linux box is the one you used
when installed the Oracle software (you own the files), you can connect as sys internally, without the need to supply a password.

$ $ sqlplus / as sysdba
SQL> shutdown immediate;
SQL> exit;

5. Stop the Database Listener with the following command.

$ lsnrctl stop <SID>

6. Edit the DB parameter file (init<SID>.ora) in the database to add the following parameter.
$cd <base directory>/db/tech_st/11.1.0/dbs
$vi init<SID>.ora
add (_disable_fast_validate=TRUE).

7. Set pga size in the init parameter file (init<SID>.ora).

Change the value of the parameter to pga_aggregate_target=2G.

Add parameter (_pga_max_size=104857600).

8. Start the Database Listener. If the command fails, source the Database environment file, ' <SID>_<hostname>.env '.

$ lsnrctl start <SID>

9. Restart the database.

Change to the directory where the parameter file exists:

$ cd <Base Directory>/db/tech_st/11.1.0/dbs
$ sqlplus / as sysdba
SQL> startup pfile= ‘/<Base Directory>/db/tech_st/11.1.0/dbs/init<SID>.ora’

10. Enable maintenance mode using the adadmin tool.

1. Note the values for the following environment variables. These values are used in the next step while using the adadmin tool.
$ echo $ORACLE_HOME
<Base Directory>/apps/tech_st/10.1.2
$ echo $ORACLE_SID
<SID>
$ echo $APPL_TOP
<Base Directory>/apps/apps_st/appl
$ echo $INST_TOP
<Base Directory>/inst/apps/<SID>_<hostname>

2. Run the adadmin tool to enable maintenance mode for the environment.

Follow the instructions in the provided Adpatch document (attached to My Oracle Support Doc ID 1951739.1), which explains how to
use the adadmin tool. For more information on the AD Administration utility, refer to <Document 109667.1>.

11. Use AutoPatch (adpatch) to apply R12.AD.B.DELTA.3 Patch 9239089.

Follow the pre-install steps described in the patch readme file and in <Document 1077769.1>. For more information about the AutoPatch
19 of 31
 (adpatch) utility. Refer to <Document 109666.1>.

1. Set the database environment.

$ cd <Base Directory>/db/tech_st/11.1.0
$ . ./<SID>_<hostname>.env

2. Create a directory in $ORACLE_HOME/appsutil/admin.

$ cd $ORACLE_HOME
$ mkdir -p appsutil/admin
$ cd appsutil/admin/
$ chmod 775.

3. Copy adgrants.sql from this patch directory (where patch 9239089 is downloaded) to $ORACLE_HOME/appsutil/admin.

$ cd $ORACLE_HOME/appsutil/admin/
$ cp <directory path where patch in unloaded>/admin/adgrants.sql.

4. Log in to sqlplus and run adgrants.sql using the apps schema password.

$ sqlplus / as sysdba
Sql> @<Base Directory>/db/tech_st/11.1.0/appsutil/admin/adgrants.sql <apps passowd>

12. Apply patch 9239089 using the adpatch tool.

Enter the directory where your Oracle Applications patch has been unloaded.
The default directory is [<Base Directory>/apps/apps_st/appl] : <path of directory where patch is unloaded>.

13. Compile APPS schema.

Run adadmin > Compile/Reload Applications Database Entities menu >Compile APPS schema.
Choose "No" at the following prompt:
Run Invoker Rights processing in incremental mode [No].

14. Apply patch 9239090 using the adpatch tool.

Enter the directory where your Oracle Applications patch has been unloaded.
The default directory is [<Base Directory>/apps/apps_st/appl] : <path of directory where patch is unloaded>.

Similarly, apply the following patches using the adpatch tool:

patch 9239095
patch 9817770
patch 9966055

15. Remove the following parameter from the init<SID>.ora file.

_disable_fast_validate=TRUE
Path for parameter file (init<SID>.ora): <Base Directory>/db/tech_st/11.1.0/dbs/init<SID>.ora

16. Disable maintenance mode using the adadmin utility.

Source the application environment file.

$ cd $APPL_TOP
$ . ./APPS<SID>_<hostname>.env
$ adadmin
Follow the instructions in the provided Adpatch document (attached to My Oracle Support Doc ID 1951739.1), which explains how to use the
adadmin tool. For more information on the AD Administration (adadmin) utility, refer to <Document 109667.1>.
20 of 31
 Verify that all patches for upgrading the environment to the 12.1.3 release have been applied successfully.

17.

3. Post Patch Application Steps

After you have upgraded to Oracle E-Business Suite Release 12.1.3, perform the following post-update steps to update all database tier nodes
with the code level, provided by Oracle E-Business Suite Release 12.1.3. For further information on post installation steps, refer to <Document
1080973.1> under the section “Post-Update Steps”.

1. Application tier:

1. When signed in as the application user, run the environment file for the current APPL_TOP.

$ . ./<Base Directory>/apps/apps_st/appl/APPS<SID>_<hostname>.env

2. Run AutoConfig on the Application tier.

$ $INST_TOP/admin/scripts/adautocfg.sh

Provide the apps user password when asked and press Enter.

3. Run the admkappsutil.pl utility to create the file appsutil.zip in the <INST_TOP>/admin/out directory.

21 of 31
 Verify the creation of the appsutil.zip file.

2. Database tier:

1. As the ORACLE user, run the environment (UNIX) file for the current ORACLE_HOME.

2. Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>.

3. Uncompress the appsutil.zip under the <RDBMS ORACLE_HOME>.

4. Run AutoConfig on the <RDBMS ORACLE_HOME>.

Change to the directory below and run adautocfg.sh:

<$ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/

22 of 31
 Provide the apps user password.

Note: For details on how to run AutoConfig on the database tier and how to transfer the AutoConfig updates from the APPL_TOP
to the RDBMS ORACLE_HOME, refer to Using AutoConfig to Manage System Configurations in Oracle Applications Release 12,
<Document 387859.1>, Section 2, Step 3, Patching AutoConfig.

3. Verify the release version:

Connect to sqlplus with the following command:

$ sqlplus <apps user>/<apps pwd>@SID
Run the following sql:
select release_name from fnd_product_groups;

23 of 31
4. Restart the application services:

Change to $ADMIN_SCRIPTS_HOME
Run adstrtal.sh using the apps user ID and password.
$ adstrtal.sh <apps>/<apps pwd>

If all services are enabled, the process will exit with status 0.

5. Recompile Invalid Objects:

Recompile all invalid objects in the environment. After recompilation, verify invalid objects in the database with the following command.
SELECT * FROM all_objects
WHERE status ='INVALID';

24 of 31
 After upgrading to the 12.1.3 release, users can now access the Oracle E-Business Suite Login page from the following URL:

http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLogin

Top

6. Steps for Applying OPH 12.1.3.1 PIM Rollup Patch1

This section discusses applying the PIM Post 12.1.3.1 Rollup Patch1. This process includes applying 13385260:R12.EGO.C as well as its
dependent patches. This section explains in detail which patches to apply and how to apply them.

1. Download the Patches Required

p10254013_R12.BNE.B_R12_GENERIC.zip

p11819064_R12.FND.B_R12_LINUX.zip

13385260_R12.EGO.C_R12_LINUX.zip

Create a directory in which to download the above listed patches and unzip them.

2. Install patches

1. Set the Application Environment.

$ cd <base directory>/apps/apps_st/appl/
$ . ./APPS<SID>_<hostname>.env

2. Enable maintenance mode for the environment using the adadmin tool.
25 of 31
 1. Note the values for the following environment variables. These values are used in the next step while using adadmin.

$ echo $ORACLE_HOME
<Base Directory>/apps/tech_st/10.1.2
$ echo $ORACLE_SID
<SID>
$ echo $APPL_TOP
<Base Directory>/apps/apps_st/appl
$ echo $INST_TOP
<Base Directory>/inst/apps/<SID>_<hostname>

2. Run the adadmin tool to enable maintenance mode for the environment.

Follow the instructions in this document for using the adadmin tool. For more information on the AD Administration (adadmin) utility,
see <Document 109667.1>.

3. Apply patch 11819064:R12.FND.B using AutoPatch. For more information on the AutoPatch (adpatch) utility, refer to <Document
109666.1>.

Note the path of the directory where the patch is unloaded, then run the adpatch tool:

Provide the directory where your Oracle Applications patch has been unloaded while running adpatch tool.
Similarly, apply the following patches using the adpatch tool.

10254013:R12.BNE.B
13385260:R12.EGO.C

4. Disable maintenance mode for the environment using adadmin.

Follow the instructions in the provided Adpatch document (attached to My Oracle Support Doc ID 1951739.1), which explains how to use the
adadmin tool. For more information on the AD Administration (adadmin) utility, see <Document 109667.1>

After applying the PIM Post 12.1.3 Rollup Patch1, you can access the Oracle E-Business Suite Login page from the following URL:
http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLogin .

26 of 31
Top

7. Install the Oracle E-Business Suite Integrated SOA Gateway (ISG)

This document explains how to install the Oracle E-Business Suite Integrated SOA Gateway (ISG). The installation process requires you to follow
certain steps in two documents:

Installing Oracle E-Business Suite Integrated SOA Gateway, Release 12 (Doc ID 556540.1)

Upgrading to the Latest OracleAS 10g 10.1.3.x Patch Set in Oracle E-Business Suite Release 12 (Doc ID 454811.1)

Follow the installation steps in Doc ID 556540.1and Doc ID 454811.1 as described below.

Doc ID 556540.1

Perform the following steps:

1. Enabling Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3 Upgraded From Oracle E-Business Suite Release 12.1.X.

1.1 Upgraded with Oracle Application Server 10g Release 3 (10.1.3) Patch Set 5 (10.1.3.5.0).

1. Follow the instructions on My Oracle Support Knowledge Document 454811.1 to upgrade your system to Oracle
Application Server 10g Release 3 (10.1.3) Patch Set 5 (10.1.3.5.0).

Doc ID 454811.1

Perform the following steps, including all substeps, unless a substep is specifically excluded:

27 of 31
Section 1: Introduction

Section 2: Pre-Installation Steps

Step 1

Step 2

Steps 3 and 4: Skip these steps, since your environment is 12.1.3, which is greater than 12.1.1.

Step 5: This step is for AIX customers only. Skip this step if you are not an AIX customer.

Step 6

Step 7

Section 3: Apply OracleAS 10g Release 3 (10.1.3.0) Patch Set 5 (10.1.3.5.0) - Skip any OS specific steps which are not applicable.

Section 4: Apply Any Additional OracleAS 10g Patches - apply both patches listed (patches 8999551 and 12965674).

Section 5: Apply Any Additional Patches (SOA Gateway customers only)

Doc ID 556540.1

Perform the following step:

3. Source the file $INST_TOP/ora/10.1.3/.env and then apply the following patches to the Oracle Application Server 10.1.3.5 Oracle Home:

Doc ID 454811.1

Perform the following step, including all substeps:

Section 6: Post-Installation Tasks

Doc ID 556540.1

Perform the following step, including all substeps:

1.2 Configuring Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3

Note: Decide during this step whether or not to use the SAML Token option.

Top

8. Troubleshooting Tips

28 of 31
Below are some common issues you might encounter during the above installation process and their resolutions.

1. adadmin: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory.

Source env with $APPL_TOP/APPS_<context_name>.env

$ cd $APPL_TOP
$ pwd
<Base Directory>/apps/apps_st/appl
$ . ./APPS<SID>_<hostname>.env

2. AutoPatch error:

AutoPatch stores backup files under your patch directory. Because of this, your patch directory must be writable.

Solution:
Change the permissions of your patch directory so that the user currently running the autopatch tool has write access.
$ cd <Path where current patch is unloaded>
$ chmod 777.
Try applying the patch using adpatch again.

3. If you receive the following error while launching the nedit:

Error:
nedit: the current locale is utf8 (en_US.UTF-8)
nedit: changed locale to non-utf8 (en_US)
X connection to localhost:10.0 broken (explicit kill or server shutdown).

Reason: There is no .Xauthority file in location (/root).

When you switch to the root user, using SUDO Xwindows commands will not work if the .Xauthority file is not present in the root.

Solution:
Change the permissions for the .Xauthority file in /home/<user>.
Copy the file to /root.

4. Post install check failed on the HTTP server.

29 of 31
Oracle HTTP Server Patch (on OEL 5 and RHEL 5 only)

Download and apply the patch 6078836 from My Oracle Support to fix an issue with the Oracle HTTP Server bundled with the E-Business
Suite technology stack. Perform the following command as root:

[root@ebs121 scripts]# cd /stageR12

[root@ebs121 stageR12]# unzip p6078836_101330_LINUX.zip
Archive: p6078836_101330_LINUX.zip
   creating: 6078836/
inflating: 6078836/libdb.so.2
inflating: 6078836/README.txt
[root@ebs121 stageR12]# mv /usr/lib/libdb.so.2 /usr/lib/libdb.so.2.6078836
mv: cannot stat '/usr/lib/libdb.so.2': No such file or directory
[root@ebs121 stageR12]# cd 6078836
[root@ebs121 6078836]# cp libdb.so.2 /usr/lib

All startup and shutdown scripts in Oracle Applications 11i(11.5.10) are located in $COMMON_TOP/admin/script/$CONTEXT_NAME, where
COMMON_TOP is also referred to as OAD_TOP and CONTEXT_NAME is your SID_hostname. For example, if the SID of the instance is
'VISION' and the hostname of the machine is 'machine1', then your CONTEXT_NAME is VISION_machine1.

The script to start/stop the Web Server is adapcctl.sh where ad (application dba), apc (apache), ctl (control) and sh stands for shell script.
Here is the syntax:

adapcctl.sh {start|stop|status}
[root@ebs121 bin]# cd /d01/oracle/VIS/inst/apps/VIS_ebs121/admin/scripts
[root@ebs121 scripts]# ./adapcctl.sh status

You are running adapcctl.sh version 120.7.12010000.2

Checking status of OPMN managed Oracle HTTP Server (OHS) instance ...

30 of 31
 Processes in Instance: VIS_ebs121.ebs121.gerardnico.com
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group          | OC4J:oafm          |   18880 | Alive
OC4JGroup:default_group          | OC4J:forms         |   18814 | Alive
OC4JGroup:default_group          | OC4J:oacore        |   18722 | Alive
HTTP_Server                      | HTTP_Server        |     N/A | Down
[root@ebs121 scripts]# ./adapcctl.sh start

You are running adapcctl.sh version 120.7.12010000.2

Starting OPMN managed Oracle HTTP Server (OHS) instance ...

adapcctl.sh: exiting with status 0

adapcctl.sh: check the logfile /d01/oracle/VIS/inst/apps/VIS_ebs121/logs/appl/admin/log/adapcctl.txt for more information ...

[root@ebs121 scripts]# ./adapcctl.sh status

You are running adapcctl.sh version 120.7.12010000.2

Checking status of OPMN managed Oracle HTTP Server (OHS) instance ...

Processes in Instance: VIS_ebs121.ebs121.gerardnico.com

---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group          | OC4J:oafm          |   18880 | Alive
OC4JGroup:default_group          | OC4J:forms         |   18814 | Alive
OC4JGroup:default_group          | OC4J:oacore        |   18722 | Alive
HTTP_Server                      | HTTP_Server        |   24735 | Alive

Top

9. References

Oracle E-Business Suite Installation Guide: Using Rapid Install

Oracle E-Business Suite Release 12.1.3 Readme, <Document 1080973.1>

Oracle E-Business Suite Applications DBA Readme, Release 12.1.3 (R12.AD.B.DELTA.3, Patch 9239089), <Document 1077769.1>

Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12, <Document 387859.1>

What is AD Administration on APPS 11.0.x ? <Document 109667.1>

Release 10.7 to 11.0.3 : What is adpatch ? <Document 109666.1>

Top

31 of 31