Skip Headers
Oracle® Life Sciences Data Hub Installation Guide
Release 2.1.4

Part Number E18152-05
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

4 Upgrading the Database and Patching Oracle Applications

This section contains the following topics:

Oracle Applications includes the Oracle 9.2.0.6 (9i) Database. However, Oracle Life Sciences Data Hub (Oracle LSH) 2.1.4 requires the Oracle 11gR2 Database Server, which requires Oracle Applications ATG RUP7, which is not supported on Oracle Database 9.2.0.6 but is supported on 9.2.0.8. Therefore you must upgrade the Oracle Database you installed during the Oracle Applications Rapid Install and Oracle Applications itself in the order given.

Note:

Oracle recommends that you make a backup of Oracle Applications and the existing database before you upgrade the database.

Upgrade the Database to 9.2.0.8

To upgrade the 9.6.0.6 database you installed during the Oracle Applications installation, apply patch set 9.2.0.8 (4547809) for your operating system, using the instructions in My Oracle Support document 216550.1, Interoperability Notes: Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0).

Note:

There is no need to run Autoconfig as described in document 216550.1 because you will immediately upgrade the database.

Apply Required Oracle Applications Patches

Install the following patches using Autopatch (see "How to Use AutoPatch").

Note:

Oracle recommends taking a full backup at this point.

Note:

If you are running on Solaris and get an error when starting Forms (required for some Oracle LSH system administration tasks), see My Oracle Support document 394587.1, Access Denied With Code 400 When Starting Forms or Calling MOD_PLSQL.

If the Oracle Discoverer release that comes with Oracle Applications fails on startup, see My Oracle Support document 421923.1, How To Prevent Adstrtal.Sh From Trying To Start/Stop Discoverer 4i. However, this version of Oracle Discoverer is not used for Oracle LSH; see Installing Oracle Discoverer 10.1.2.3.

Upgrade to J2SE 6

After applying 11i.ATG_PF.H.RUP7 ( Apply Required Oracle Applications Patches) you can upgrade to J2SE 6, which includes JDK. Use My Oracle Support article 401561.1, Using JDK Version 6 with Oracle E-Business Suite 11i, Releases 11.5.10; see "Searching for Knowledge Articles by ID".

For J2SE client deployment, use My Oracle Support article 290807.1, Deploying Sun JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite 11i.

Upgrade the Database to 11.2.0.1

Follow instructions for upgrading the database in My Oracle Support article 1265268.1, Interoperability Notes Oracle E-Business Suite Release 11i with Oracle Database 11g Release 2 (11.2.0). The following steps are not required for Oracle LSH:

Apply Database Patches

In addition, install the following patches using Autopatch (see "How to Use AutoPatch").

Note:

Oracle recommends taking a full backup at this point.

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.

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 ildv214:

SID_LIST_ildv214 =
  (SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = ildv214)
      (ORACLE_HOME= /slot/ems6636/oracle/ildv214db/11.2.0)
      (SID_NAME = ildv214)
    )
    (SID_DESC =
      (GLOBAL_DBNAME = ildv214.us.oracle.com)
      (ORACLE_HOME= /slot/ems6636/oracle/ildv214db/11.2.0)
      (SID_NAME = ildv214)
    )
    (SID_DESC =
      (SID_NAME = PLSExtProc)
      (ORACLE_HOME = /slot/ems6636/oracle/ildv214db/11.2.0)
      (PROGRAM = extproc)
    )
  )

Change Default Password Settings

Oracle 11g includes new default password-related settings.

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 document 230672.1, Cloning Oracle Applications Release 11i with Rapid Clone.