3 Installing and Patching Oracle Applications and Oracle Database

This section includes the following topics:

Section 3.1, "Install Oracle Applications 12.1.1"
Section 3.2, "Upgrade Oracle Applications to R12.1.3 and Apply Patches"
Section 3.3, "Upgrade the Oracle Database and Oracle Warehouse Builder to 11.2.0.4"
Section 3.4, "Edit listener_ifile.ora"
Section 3.5, "Change Default Password Settings"
Section 3.6, "Increase JVM Memory"
Section 3.8, "Clone the Environment (Optional)"
Section 3.9, "Install Oracle Warehouse Builder on Oracle Database 11gR2"
Section 3.10, "Create an Oracle Warehouse Builder Repository"

3.1 Install Oracle Applications 12.1.1

To install Oracle Applications 12.1.1, use Oracle E-Business Suite Installation Guide: Using Rapid Install Release 12 (12.1.1) (Part E12842-04)).

Note:

Oracle LSH has been tested ONLY on Release 12.1.3 of Oracle Applications. If more recent releases have become available, do NOT install them unless explicitly instructed to do so by an Oracle LSH-specific note or alert on My Oracle Support.

3.1.1 Oracle LSH UTF8 Requirements

Oracle LSH has the following character set-related required settings:

Database character set=UTF8. Oracle Applications Rapid Install prompts you for the database character set. You MUST set this value to UTF8. A value of UTF8 is REQUIRED. This is the ONLY opportunity you have to set this value, and you CANNOT change it later.
NLS_CHARACTERSET=UTF8. When you set the database character set to UTF8 during Oracle Applications Rapid Install, it automatically sets NLS_CHARACTERSET to UTF8 as well, which is correct.
NLS_LENGTH_SEMANTICS=BYTE. The default value for NLS_LENGTH_SEMANTICS is BYTE. Do not change this value. To use character semantics, set the LHS profile Use Character Semantics for Workarea Installation to Yes. See the chapter on setting profile values in the Oracle Life Sciences Data Hub System Administrator's Guide for information.

3.2 Upgrade Oracle Applications to R12.1.3 and Apply Patches

3.2.1 Install Patches Using Autopatch

Install the following patches using Autopatch (see "How to Use AutoPatch") to upgrade from R12.1.1 to R12.1.3:

9239089 Oracle Applications DBA 12.1.3 Product Release Update Pack
9239090 Oracle E-Business Suite 12.1.3 Release Update Pack
10222869 Oracle Applications Framework patch
12661509 for compatibility with Internet Explorer 8.
11781531, NOT ABLE TO ADD HTTPS URL TO FAVORITES LINK IN 12.1.2. HTTP IS PRE-PENDED TO URL
11832737, which is a forward port of patch 9908921 to Oracle Applications 12.1.3 fixing the intermittent FND_NO_DATABASE_CONNECTION error observed in the new home page.

3.2.2 Download and Install the Software Development Kit for Java

The E-Business Suite Software Development Kit for Java ships as patch 17269917 (p17269917_R12_GENERIC.zip) on the Oracle Health Sciences Life Sciences Warehouse media pack.

The .zip file contains:

The Oracle E-Business Suite SDK for Java file, fndext.jar
README.txt
Javadoc for Oracle E-Business Suite SDK for Java
An Apache Ant XML file named txkEbsSdkConfig.xml

Extract fndext.jar.
Copy the extracted fndext.jar file and the txkEbsSdkConfig.xml file to a directory such as/home/user1/ebssdk on the WebLogic server.
Copy the Javadoc to any appropriate location for convenient reference.

Note:

Check My Oracle Support article 1138053.1, Oracle Life Sciences Data Hub and Oracle Clinical Development Analytics Known Install and Configuration Issues to see if any other patches have become required. Do not apply additional patches unless they have been tested with Oracle LSH and listed in article 1138053.1. See "Finding More Information".

Note:

Oracle recommends taking a full backup at this point.

3.3 Upgrade the Oracle Database and Oracle Warehouse Builder to 11.2.0.4

Oracle Applications Release 12.1.1 includes Oracle Database 11.1.0.7. To use Oracle LSH Release 2.4, you must upgrade to Oracle Database 11.2.0.4. The process includes upgrading Oracle Warehouse Builder (OWB) to 11.2.0.4. The software is available as patch 13390677.

Follow My Oracle Support document 1058763.1, Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 to upgrade Oracle Database to 11.2.0.4.

Note:

If a new Oracle Database patch set for 11gR2 is released in future, the article number 1058763.1 may be used for the new release. If the article applies to a newer release, it should display the new article number for the 11.2.0.4 Interoperability note. Do not install newer Oracle Database patch sets unless explicitly instructed by an Oracle LSH-specific note or alert on My Oracle Support.

Note:

Be sure to install the Oracle Examples, which are included in the media pack and include Oracle Text. Oracle Text is required by Oracle Thesaurus Management System for the Oracle LSH classification system.

Note:

Oracle recommends taking a full backup after the upgrade.

3.4 Edit listener_ifile.ora

You need to configure the database TNS listener to allow OWB to communicate with the database. Instead of making all the required changes in the listener.ora file, which is overwritten when you run Autoconfig, make the changes in the listener_ifile.ora file, which is called from listener.ora.

Check variable $TNS_ADMIN for the location of listener.ora. The file listener_ifile.ora is in the same location.

Edit listener_ifile.ora to make TNS listener-related changes. For example, if the database SID is xyz22:

SID_LIST_xyz22 =
  (SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = xyz22)
      (ORACLE_HOME= /slot/ems6636/oracle/xyz22db/11.2.0)
      (SID_NAME = xyz22)
    )
    (SID_DESC =
      (GLOBAL_DBNAME = lshdb.your_company.com)
      (ORACLE_HOME= /slot/ems6636/oracle/xyz22db/11.2.0)
      (SID_NAME = xyz22)
    )
    (SID_DESC =
      (SID_NAME = PLSExtProc)
      (ORACLE_HOME = /slot/ems6636/oracle/xyz22db/11.2.0)
      (PROGRAM = extproc)
    )
  )

3.5 Change Default Password Settings

Oracle 11gR2 includes new default password-related settings.

Edit init.ora to turn off case-sensitive database logon as follows:
```
sec_case_sensitive_logon=false
```
To prevent database password expiration, log in to SQL*Plus as a superuser and enter:
```
ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;
```

3.6 Increase JVM Memory

Oracle recommends a minimum Java Virtual Machine (JVM) setting of 2048M instead of the default size of 512M.

You must make this change through Oracle Applications Manager. If you do it manually, your changes will be lost when you run AutoConfig.

To increase this setting, do the following:

Open your web browser.
Enter the eBusiness Suite SSWA (Self-Service Web Application) URL as follows:

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

For example:

http://host_0066.example.com:8000/OA_HTML/AppsLogin

The Applications Login screen appears.
Log in as sysadmin.

An E-Business Suite screen opens.
Click System Administration in the left-hand column under Navigator. The system refreshes the page and adds a column of links on the right.
Under Oracle Applications Manager in the Navigator pane, click Dashboard. The Applications Dashboard screen opens.
Click Sitemap to go to the Sitemap tab.
Under System Configuration, click AutoConfig. The AutoConfig screen opens.
Under Context Files, click the Edit Parameters icon for the Application Tier. The Context File Parameters screen opens.
From the Search drop-down list, select OA_VAR.
In the field next to the Search drop-down list, enter the parameter name s_oacore_jvm_start_options and click Go.
In the Value field for s_jvm_options, change the value from:

-Xmx512M -Xms128M -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB

to:

-Xmx2048M -Xms128M -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB

Note the changed value is in bold above.
Run AutoConfig. See My Oracle Support article 387859.1, Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release 12.
Stop and start the Apache server for the new value to take effect.

3.7 Secure the Oracle Applications Installation

Follow instructions in My Oracle Support article 403537.1, Secure Configuration Guide for Oracle E-Business Suite Release 12 to set up Oracle Applications securely.

3.8 Clone the Environment (Optional)

If you plan to create another Oracle LSH environment on the same platform, you can clone your installation at this point. You cannot clone it after you have installed OWB, TMS, or iAD. Refer to My Oracle Support article 406982.1, Cloning Oracle Applications Release 12 with Rapid Clone.

3.9 Install Oracle Warehouse Builder on Oracle Database 11gR2

Oracle Warehouse Builder is part of the standard installation on all hosts running Oracle Database 11g Release 2. When Oracle Database is installed, you must only unlock the OWBSYS and OWBSYS_AUDIT accounts. The OWBSYS schema contains all Warehouse Builder repository metadata, and the OWBSYS_AUDIT schema is used by the Warehouse Builder Control Center Agent to access the heterogeneous execution audit tables of the OWBSYS schema.

3.10 Create an Oracle Warehouse Builder Repository

Oracle Warehouse Builder 11.2.0.4 is required for Oracle LSH's execution system, which is also used by Oracle DMW. It is included in Oracle Database 11.2.0.4.

Follow instructions in Oracle Warehouse Builder Installation and Administration Guide 11g Release 2 (11.2) (Part E17130-03), which is included on the media pack, Chapter 4, Section 3, "Creating the First Workspace in the Repository on Linux".

Important:

During the creation of the Workspace Repository, the value of both the Owner's Username and Workspace name should be CDR_RTREPOS. This is required for a successful Oracle LSH 2.4 installation.