Preface

This guide describes how to install Oracle Life Sciences Data Hub (Oracle LSH) Release 2.4.

Audience

This guide is written for people with the skill set described below. If your staff lacks these skills, Oracle recommends that you engage Oracle Consulting.

Required Skills

Installing Oracle LSH requires a level of knowledge equivalent to having mastered the material in Oracle's DBA Architecture and Administration courses.

You must be able to do the following in SQL*Plus:

• Read and edit scripts

• Run scripts and review log files for Oracle errors

You must be able to do the following in UNIX:

• Install Oracle software and patches

• Identify space on a file system for Oracle database tablespaces

• Set and use environment variables

• Edit files using vi or another editor

• Run scripts and review log files

You also need expertise in:

• Network administration

• Cluster file systems—when not using Oracle Automated Storage Manager (ASM) or Oracle Cluster File System (OCFS)

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

How to Use AutoPatch

For complete information on using AutoPatch and an explanation of the Oracle Applications patching system and terminology, see:

• Oracle Applications Maintenance Utilities Release 12 (12.1.1)

• Oracle Applications Maintenance Processes Release 12 (12.1.1)

AutoPatch has a command prompt interface.

The basic steps required to apply a patch using AutoPatch are as follows. See the books mentioned above for detailed instructions.

1. Set the environment. You must set the environment to apply the configuration parameters that define your system. See Oracle Applications Maintenance Utilities Release 12 (12.1.1) for further information.

2. Unzip patches. Create a patch top directory, if it doesn't already exist. Download the patch and unzip it into this directory.

3. Review information in the readme file. The readme file contains instructions for applying the patch, including any prerequisite patches and/or manual steps.

4. Shut down services. If you are applying the patch to a node that contains the Concurrent Processing Server, Web Server, or Forms Server, you must shut down the Concurrent Managers, Web Server Listeners, or Forms Server Listeners respectively.

5. Enable Maintenance Mode. Use the Change Maintenance Mode option in AD Administration to enable maintenance mode. See "Change Maintenance Mode" in Oracle Applications Maintenance Utilities.

   Note:

   Maintenance mode enhances patching performance but restricts users' access to Oracle Applications.

6. Start AutoPatch. AutoPatch is located in the AD_TOP/bin directory. However, you start it from the directory that contains the unzipped patch files. Use the following command:

   $ adpatch

   You can customize the way AutoPatch runs by adding arguments to the command line. See "Command Line Arguments" in Oracle Applications Maintenance Utilities.

7. Respond to prompts. Respond to the AutoPatch prompts for information about your system.

8. Apply driver. Patches contain a single unified driver (u).

9. Exit AutoPatch. When the patching process is complete, AutoPatch displays a message informing you that the process has been completed successfully. If the process did not run to completion, check the log file(s) and determine what caused the problem.

   The primary log file is located in APPL_TOP/admin/Oracle SID/log default name adpatch.log. In addition, some patch tasks may create separate log files in the same directory. If the patching process used multiple workers, each worker creates its own log file.

10. Disable Maintenance Mode. Use the Change Maintenance Mode menu of AD Administration to disable maintenance mode. See "Change Maintenance Mode" in Oracle Applications Maintenance Utilities.

11. Restart server processes. After verifying that the patch was applied successfully, start all server processes and allow users to access the system.

12. Pre-allocate space for packages, functions, and sequences (optional). If AutoPatch has modified Oracle Applications database objects, you may want to run ADXGNPIN.sql and ADXGNPNS.sql to allocate space ("pin") for new packages and sequences in the Oracle System Global Area. These scripts are located in AD_TOP/sql. See "Pre-allocating Space for Packages and Functions" in Oracle Applications Maintenance Processes.

13. Delete or archive AutoPatch backup files. Once you have tested the patched system, you can delete the backup copies of files from the patch top directories to recover disk space, as necessary. Oracle recommends archiving these files if you have space available.

Oracle CPU Security Updates

Oracle Corporation publishes a CPU Security Update patch quarterly. Install these patches on every computer with an Oracle Home. Check My Oracle Support's Oracle Clinical Knowledge page for information on the latest patch tested with Oracle Health Sciences applications.

Finding More Information

Oracle Help Center

The latest user documentation for Oracle Life Sciences Data Hub is available at http://docs.oracle.com/en/industries/health-sciences/lsh-248.

My Oracle Support

The latest release notes, patches and white papers are on My Oracle Support (MOS) at https://support.oracle.com. For help with using MOS, see https://docs.oracle.com/cd/E74665_01/MOSHP/toc.htm.