Skip Headers
Oracle® Healthcare Transaction Base Installation Guide
Release 6.1.1

Part Number E37798-03
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

3 Installing Oracle Healthcare Transaction Base

Depending on the installation flavor (primarily OS/Database/E-biz suite, and HTB version) the list of patches varies. The following information details an HTB version 6.1.1 (R12.HC_PF.A) installation. It is always important to perform an analysis of the patches according to the Readme document delivered with the products you are installing.

You can locate all the information and reference links, related to Oracle E-Business Suite (12.1.1) installation and documentation, using My Oracle Support Article ID: 761566.1.

Note:

For the patching process it is sometimes customary for installers to follow the links in My Oracle Support to new patches that supersede those included as prerequisites in the Readme of an Oracle product. It is very important that any such action be taken only when the installer has direct knowledge that the superseding patch should be applied. An installer should never move to a newer version of a patch that is specifically called out by a Readme document because of the notes displayed within My Oracle Support. Doing so may jeopardize the installation of HTB.

This section contains the following topics:

3.1 Validating OS Installation

Verify that your operating system is installed according to the requirements of Oracle Applications: Installation Guide: Using Rapid Install document at http://docs.oracle.com/cd/B53825_01/current/acrobat/121oaig.pdf and Oracle Applications Release Notes, 12.1.1 document (My Oracle Support Article ID: 761566.1). Both have specific OS requirements that must be met prior to the installation of Oracle E-Business Suite using Rapid Install (rapidwiz). For example, when installing Red Hat Linux, include Legacy Software Development and X Software Development packages.

Once the OS installation is complete, refer to Oracle Applications Release Notes, 12.1.1 document (My Oracle Support Article ID: 761566.1) for additional package and configuration requirements for the installation of the 12.1.1 Oracle Applications E-Business Suite. Do not skip any OS patches that must be applied prior to the installation of E-Business Suite. Oracle has published patches for compatibility with certain operating system versions.

3.2 Installing Oracle R12 E-Business Suite using Rapid Install

If you are upgrading your Oracle Applications E-Business Suite Release from release 11i with HTB version 5 to release R12 with HTB version 6.1.1, refer to the next section Upgrading Oracle Applications with HTB.

Install 12.1.1 Oracle Applications E-Business Suite from a local or NFS mounted staged area. Note that once the installation is complete, this staged area can be reclaimed for additional space. Refer to Installing Oracle Applications: A Guide to Using Rapid Install document for the Rapidwiz installation. If you do not have a staged area, go to otn.oracle.com and search for the R12 Oracle E-Business Suite 12.1.1 download. If you loaded your staged area from CDs, verify that you have version 12.1.1. or later of Rapidwiz. If you have an older version or you are unsure of your version, you must download the Start Here CD set from http://edelivery.oracle.com/ and replace these files in your staged area. Perform the following steps to download newer version of the RapidWiz Start Here CD from http://edelivery.oracle.com/. Note that a script-enabled browser is required for this page to function properly.

  1. Select English > Continue

  2. Select: Product Pack: Health SciencesPlatform: For example, Linux x86

  3. Click Go

  4. Select Oracle Healthcare 6.1.1 Media Pack for Linux x86

  5. Click Continue

  6. Click Download for: Oracle Applications Release 12.1.1 Rapid Install Start Here (Download all required CDs based on 12.1.1 product installation requirements at your site)

The E-Business Suite installation can be performed on a single or multiple node configuration. The Rapidwiz wizard walks you through the process. Note that you should never use the same user for both the applications and database nodes, regardless of the type of installation configuration. Oracle Inventory must be accessible by these users during HTB installation. There are other considerations as well during the setup and use of the environments.

The users for the E-Business Suite installation are recommended to be appl<database name> and ora<database name> with a group of dba. Take due care in planning the appropriate user and group configuration so that you do not have read/write access problems during your installations. One possible compromise is to create an appl<database name> user for Oracle Applications and an oracle user for the database. The oracle user can belong to multiple groups so assigning both dba and oinstall may help you avoid problems. Always make sure you back up your oraInventory and related files so that you can recover the previous inventory if required.

3.3 Patching Oracle R12 Instance

Once the Oracle E-Business Suite installation is complete, you should be able to log in to applications on the HTTP port defined. By default, the port number is 8000. Verify that the installation is complete and Oracle Apps is up and running before continuing with the patching process. Once verified, shut down Oracle Applications by running the adstpall.sh script, passing the APPS user and password used during the installation (apps by default).

When loading patches for a product or prerequisites for a product you must take into whether you require any additional language support. If you are implementing Multiple Language Support in HTB product, you should also download and apply all necessary language patches for the languages that you registered while installing Oracle E-Business Suite.

This section contains the following topics:

3.3.1 Upgrade Database

The 12.1.1 staged software installs 11.1.0.7 version of the Oracle Database. Upgrade your database to 11.2.0.3 using My Oracle Support Article ID: 1058763.1.

3.3.2 Upgrade E-Business Suite

Upgrade your E-Business Suite 12.1.1 to 12.1.3 using My Oracle Support Article ID: 1175553.1.

3.3.3 Applications Technical Stack Patches

The 12.1.1 staged software installs a 11.1.0.7.0 version of the Oracle Application Server (10gAS) software referenced by environment variable IAS_ORACLE_HOME. For HTB version 6.1.1, Oracle requires the Oracle Applications Technical Stack component referenced by IAS_ORACLE_HOME to be upgraded to 10.1.3.5.0. All Oracle Applications E-Business Suite Release 12 certification levels can be found on My Oracle Support using navigation:

Certify > View Certifications by Product > E-Business Suite > E-Business Suite Release 12 > Select your platform > Submit

Find your Application Server platform combination and select the Other column link to review all Applications Tier components.

To upgrade your E-Business Suite Release 12 Applications Server Technical Stack to version 10.1.3.5.0, follow the following My Oracle Support Article ID 454811.1.

3.4 HTB Product Patch Application

You can use adctrl application to control the workers, if you have a worker that needs to be restarted or stopped. HTB is an off-cycle product that must be spliced in Oracle Applications. If you have already installed HTB and are only upgrading to the latest HTB release, you do not need to re-splice the three HTB related schemas into your Oracle Applications database instance. If you are upgrading from Oracle Applications Release 11i to Oracle Applications Release 12 with the Healthcare Product Suite, you need to run the splice patches to install the product directory structure into the newly created 12.1.1 APPL_TOP.

This section contains the following topics:

3.4.1 Create HTB Product Schemas

Using adsplice, create three required schemas, CTB, HCT, and HCP, using the three patches from the table below. Note that if you do not have these patches, you need to open a Service Request in My Oracle Support and request a password to download them.

See Also:

Running the adsplice Utility for information on running adsplice.

Oracle Applications E-Business Suite release 12.1.3 utilizes the Oracle Applications Tablespace Model (OATM). If you are upgrading from a previous release of Oracle Applications, Oracle recommends that you migrate to the OATM model as detailed in My Oracle Support Article ID: 258325.1

Table 3-1

Patch Number Patch Description

5497423

ADSPLICE FILES FOR ORACLE APPLICATIONS PRODUCT (CTB)

5497469

ADSPLICE FILES FOR ORACLE APPLICATIONS PRODUCT (HCT)

5497505

ADSPLICE FILES FOR ORACLE APPLICATIONS PRODUCT (HCP)


3.4.2 Apply HTB Version 6.1.1 Patches

The post installation instructions for these patches are included in the sections that follow. Take due care in reviewing the log files from this large patch as many of the objects are named such that the word "error" is included.

Table 3-2 HTB Version 6.1 Patches

Patch Number Patch Description

6446398

ORACLE HEALTHCARE FAMILY PACK A (R12.HC_PF.A)

14376817

R12.HCT.A.DELTA.3

14317443

R12.CTB.A.DELTA.3

14079734

OPTIMIZE ACT RELATIONSHIP CRITERIA BY INCLUDING DENORMALIZED COLUMNS FROM ACT (Refer to patch readme in My Oracle Support Note ID: 1459776.1, for implementing associated pre-patch data model changes)


3.4.3 Apply HTB Version 6.1 One-Off Patches

HTB one-off patches are released to My Oracle Support as they become available. The decision to apply a one-off patch should depend on the bug reported and its fix in the product. You must also consider that a Rollup (RUP) patch will contain all one-off patches from the previous releases. Review the HTB About Doc for the list of one-offs already included in the current HTB release. All one-off patches should be considered in your environment. Oracle recommends you to maintain a backup of the full environment prior to the application of patches. This not only lets you to quickly and easily revert to a pre-patched state, but also assures that you have a sufficient backup if a problem occurs during patching.

Each patch should be reviewed to determine whether any post patch application steps are required. Any post patch steps must be completed according to the Readme requirements. It is possible to merge CTB one-off patches together so that they can be applied via a single unified driver using adpatch.

Perform the following steps to determine which one-off patches are required:

  1. Log in to My Oracle Support and navigate to Patches & Updates tab.

  2. Select Advanced Search link in the Patches section.

  3. Select the Product Family Healthcare Suite.

  4. Delete release Applications R12.

  5. Add release Applications R12.

  6. Select Patch Type Any.

  7. The Updated in last field should be populated so that all patches since your last search are included. If this is the first application of one-off patches, you should calculate the number of days, weeks or months according to the official release date of HTB version 6.1

  8. Select Go and the list of patches is returned from the query in reverse chronological order.

  9. Each patch must be reviewed to determine whether it should be applied or not. The View Readme icon on the returned table lets you view Readme file delivered with the patch. Only patches that include R12.HC_PF.A Rollup 3 as a prerequisite should be applied. Note that one-off patches which have been released for prior versions of HTB should not be applied on top of your RUP3 instance. You may also see patches for other Healthcare Suite products such as Oracle Life Sciences Data Hub. These non-HTB related patches should not be applied. They also do not include R12.HC_PF.A Rollup 3 as a prerequisite.

  10. Merge this group of new HTB version 6.1 one-off patches together and apply them using adpatch.

  11. Review the log file and correct any errors or failures as necessary. If you are unable to determine the correct course of action, log a Service Request via My Oracle Support.

Once you have run this query the first time, you can set the Updated in last field to a value such as 30 days and save the query for future use. This lets you return to the Patches & Updates tab and select the Saved Searches link. If run on a regular basis you can keep a track of which patches are available for your HTB version 6.1.1 instances.

To merge several HTB one-off patches together and apply all of them as a single patch, do the following:

  1. Create a directory and unzip all the HTB one-off patches into that directory.

  2. Create a target directory in which to store the merged patch.

  3. Merge all the patches into a single universal patch using the following admrgpch command:admrgpch -s <source directory> -d <target directory> -merge_name <name of merged patch>Oracle recommends that you provide a name for the merged patch that includes both the string HTB and the date of the merge, so that the later review using the Oracle Applications Manager will differentiate this patch from other merged patches.

You can now apply the new merged patch from the target directory using the adpatch utility.

Apply patch number 9814493 and 9814032.

3.4.4 HTB Post Patch Application Steps

Once all patches are applied and all logs are reviewed and verified, turn off maintenance mode using adadmin. This enables normal operation of the R12 Oracle Applications Suite. The information that follows is taken from the HTB About Doc and Readme files and must be followed carefully. If you have any problems after completing these steps, review each step and verify that you have successfully completed its requirements. If you deviate from these steps, ensure that you complete the required configuration.

This section contains the following topics:

3.4.4.1 Allow Remote Clients to Connect to Database

The initial application of a multi-node installation via Rapidwiz restricts access to the database from any other servers. If you want to connect from your desktop or laptop using a GUI admin or query tool such as Oracle SQL Developer, perform the following process steps on your database server while logged in as the oracle database user:

  1. Change directory to ${ORACLE_HOME}/network/admin/${ORACLE_SID}_${HOSTNAME}.

  2. Update the sqlnet.ora> file by changing tcp.validnode_checking from yes to no.

3.4.4.2 Regeneration of Jar Files

To regenerate outdated or missing jar files without force option:

  1. Run adadmin

  2. From the main menu of adadmin select:Generate Application Files Menu > Generate Product Jar Files

  3. Enter No at the Do you wish to force regeneration of all jar files? prompt.

Note:

To avoid errors when loading Messaging Metadata, Oracle recommends that you force regeneratation of all the jar files using adadmin.

3.4.4.3 Make HTB Application Menus Available to Oracle Applications

Autoconfig context value settings need to be modified to main HTB Application Menus available in Oracle Applications SSWA menu structure. The recommended method to update the Applications Context file is using Oracle Applications Manager (OAM). To log in to OAM:

  1. Log in to Oracle Applications using the SYSADMIN user and System Administration Responsibility.

  2. On the menu items under Oracle Applications Manager select Dashboard.

  3. Navigate to Site Map > Administration, and select AutoConfig.

  4. Select Edit link to the right side of the Applications Context file you want to modify:

  5. Navigate to System > oacore_server > For OA_VAR s_oacore_jvm_start_options, scroll to the end of the already set values and add the following to the end. Append to the end of the s_oacore_jvm_start_options values the following additional options.

    1. Use full path names instead of $JAVA_TOP and $FND_SECURE.

    2. Replace <context name> with the actual path name in your environment and dbcfile with the correct value for your FND_SECURE dbc filename.

      -Djbo.323.compatible=true -DAdaptorCatalog=$JAVA_TOP/oracle/apps/ctb/tools/bridge/catalog.xml -DClientMode=local -DDBCFile=$FND_SECURE/<oracle_sid>.dbc -DJTFDBCFILE=$FND_SECURE/<oracle_sid>.dbc
      

      Note:

      After adding these parameters to the Applications Context file, you must rerun Autoconfig for the changes to take effect.