1. Installation Guide
  2. Installing Oracle Life Sciences Data Hub
  3. Run the Post-Installation Programs

Run the Post-Installation Programs

You must run the Oracle LSH LOB Loader and post-installation concurrent programs.

Note:

If you are using RAC, shut down all but one database node before running the post-installation programs. If you leave more than one node up, the jobs may run successfully but you may get OWB errors.

Parent topic: Installing Oracle Life Sciences Data Hub

Check That OWB Is Running Without Errors

You must have OWB running to run the post-installation programs; see Restart the OWB Service. If OWB is not running when you run the LOB Loader and Post-Installation programs, some required objects may not be created and you cannot create them by rerunning the programs after restarting OWB.

To check that the OWB service is running do the following:

  1. Change directory to $ORACLE_HOME/owb/rtp/sql

  2. Log into SQL*Plus as OWBSYS.

  3. At the SQL prompt, enter:

    @show_service.sql

The system displays the word "Available" if service is running.

To check that the OWB service is running without errors do the following:

  1. If necessary, change directory to $ORACLE_HOME/owb/rtp/sql and log into SQL*Plus as OWBSYS.
  2. At the SQL prompt, enter:

    @service_doctor.sql

The system returns a series of statements. Read them to see if any error conditions are reported. Resolve any errors.

Parent topic: Run the Post-Installation Programs

Log On to Oracle Applications

To run the jobs, you must log on to Oracle Applications as an Oracle LSH user with the following roles:

  • LSH Setup Admin

  • LSH Adapter Security Admin

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

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

    For example:

    http://appshost.your_company.com:8000/oa_servlets/AppsLogin

    The Applications Login screen appears.

  3. Log in as a user with LSH Setup Admin and LSH Adapter Security Admin privileges. An Oracle LSH page opens. Click Home from the links on the top right corner of the page to reach the Oracle Applications Home Page.
  4. Select the LSH Setup Admin Responsibility by clicking on it. Lookups appears in the second column.
  5. Click Lookups. (If necessary, click Grant This Session or Grant Always.) The Oracle Life Sciences Data Hub Lookups window opens.
  6. From the View menu, select Requests.

Parent topic: Run the Post-Installation Programs

Load the Adapter Files

Oracle LSH includes predefined adapters that control the interaction between Oracle LSH and other systems. The Oracle LSH LOB Loader concurrent program finds all the adapter SQL files and loads them into a table in Oracle LSH.

To run the Oracle LSH LOB Loader:

  1. Follow steps in Log On to Oracle Applications.

  2. Click Submit a New Request. The Submit a New Request window opens.

  3. Select Single Request and click OK. The Submit Request window opens.

  4. Click the gray LOV button on the right of the Name field. The Reports List of Values opens.

  5. Select LSH LOB Loader Concurrent Program and click OK.

  6. Click Submit. A window pops up with the job ID and asks if you want to submit another request.

  7. Click No.

To monitor the concurrent program's progress:

  1. Click Find.
  2. Click Refresh Data periodically to update the execution phase and status displayed on screen.

When the status is Complete you can view the log file by clicking the View Log button.

Note:

Always check the log file, because the phase may be Complete and the status Normal and yet the program may not have successfully completed all its tasks.

Parent topic: Run the Post-Installation Programs

Set the Tech Type Value

In a fresh installation of Oracle LSH, you need to set the Tech Type value as described below. These steps are not required in an upgrade.

  1. Log in to SQL*Plus as apps.
  2. Run the following SQL statement:

    select CDR_TECH_TYPES_ID_SEQ.nextval from dual;

Parent topic: Run the Post-Installation Programs

Run the Post-Installation Program

Note:

  • Read this whole section before you do this step. You must be very careful to SET ALL PARAMETERS CORRECTLY. You cannot change some of them after you run the job.
  • Run $ORACLE_HOME/owb/rtp/sql/show_service.sql as the OWBSYS user to check that the OWB service is running before attempting to do this step.

The Oracle LSH post-installation program takes parameter values you enter to configure your Oracle LSH instance and creates accounts and objects that Oracle LSH uses internally:

  • Sets the Oracle LSH context from the parameter values you enter (listed below).

  • Creates required FND Oracle Applications profiles for the company ID and owning location you specify.

  • Creates the Oracle LSH instance domain. This is the parent defined object that contains all the Oracle LSH Domains and other defined objects in your Oracle LSH instance.

  • Loads the predefined Oracle LSH object subtypes.

  • Creates internal adapters, defined objects that store required Parameters and other elements used by Execution Setups and Oracle LSH Workflows. Oracle LSH uses these adapters as a template in creating required elements of these defined objects.

  • Enables the job queue. (To start the queue, see the chapter "Stopping and Starting Services and Queues" of the Oracle Life Sciences Data Hub System Administrator's Guide.)

  • Configures a PL/SQL service and three service instances for internal Oracle LSH use. For information on services, see "Setting Up Services" in the Oracle Life Sciences Data Hub System Administrator's Guide.

  • Deploys standard process flows to enable the Notifications feature of LSH Workflows.

In addition to the adapter files loaded by the LOB Loader, Oracle LSH's adapters are composed of metadata elements that are Oracle LSH definitional objects. The post-installation job creates and installs these objects as follows:

  • For each adapter, the job creates an Adapter Domain, an Adapter Area within the Adapter Domain, and an Adapter Work Area within the Adapter Area. In the case of Oracle Clinical the job creates a single Adapter Domain containing an Adapter Area and Adapter Work Area for each of the specialized Oracle Clinical adapters.

  • The job creates a Program and related object definitions in each adapter's Adapter Area and object instances in its Work Area. The job adds the adapter SQL files loaded by the Oracle LSH LOB Loader job to the Source Code definition.

  • The job installs each Adapter Work Area, creating a schema dedicated to each adapter. You must assign user groups to each Adapter Area. See "Setting Up Security for Adapters" in the Oracle Life Sciences Data Hub System Administrator's Guide. Users in the user groups assigned to an Adapter Area can create and run Load Sets, Data Marts, Programs, or Business Areas based on that adapter.

Note:

  • If you run the Oracle LSH post-installation job more than once, the job upgrades the adapters.
  • The first value of the parameter utl_file_dir of the init.ora file must match the middle tier variable $APPLPTMP. Otherwise the post-installation program will fail. See Edit init.ora.

Run the Job: To run the Oracle LSH post-installation concurrent process:

  1. Click the Submit a New Request button either:

    • in the Requests window you used to monitor the Oracle LSH LOB Loader concurrent process

    • after following steps under Log On to Oracle Applications

  2. Select Single Request and click OK. The Submit Request window opens.

  3. Click the gray LOV button on the right of the Name field. The Reports List of Values opens.

  4. Select LSH: Post Installation Program and click OK. The Parameters pop-up window appears.

  5. Enter values for the following Parameters:

    Note:

    Be very careful to set these Parameters correctly. You cannot change some of them after you run the job.

    See If You Must Change a Post-Installation Job Parameter Value for details.

    • Company ID. The company ID serves as part of the primary key for all the Oracle LSH objects you define in this instance of Oracle LSH. If your company ever merges with another company and your Oracle LSH data and metadata are merged with the other company's, the company ID distinguishes the objects created in each original company and helps prevent duplicate object primary keys.

      In order to ensure that you have a unique number relative to other Oracle LSH customers, Oracle recommends that you use a number assigned to you by Oracle; see Get Your Company ID from Oracle. If you are installing multiple Oracle LSH instances, use a different Company ID for each one.

      Note:

      Be sure to enter the correct company ID. Oracle LSH uses the company ID in the internal ID for every defined object in Oracle LSH. Changing the ID requires manually removing the data in internal tables for all objects created with the original ID.

    • Owning Location. Enter the name of your Oracle Applications instance.

    • Object Sequence Start Value. Enter a single digit. The system will end all object IDs with this digit to further distinguish objects created in this Oracle LSH instance.

    • Object Sequence Start Value. Leave blank. The system will end all object IDs with the number 1.

    • Database Host Name. Enter the machine name of the database server instance.

    • Database Port Number. Enter the port number of the database server instance.

  6. Click Submit. A window pops up with the job ID and asks if you want to submit another request.

  7. Note the job ID and click No.

Monitor the Process: To monitor the concurrent process's progress:

  1. Click Find. Use the job ID to search for the process.
  2. Click Refresh Data periodically to update the execution phase and status displayed on screen.
  3. When the phase is Complete, click the View Log.

    Note:

    Always check the log file, because the phase may be Complete and the status Normal and yet the process may not have successfully completed all its tasks.

    Check the log file to make sure it did the following:

    • Set the company ID

    • Set the owning location

    • Recreated the cdr_object_id_seq with the start value you provided

    • Inserted one record each in the cdr_namings and cdr_naming_versions tables for the instance domain

      Note:

      The job does the above only the first time it runs.

    • Set the profile to check if the post-installation has been run for this site.

Parent topic: Run the Post-Installation Programs

If You Must Change a Post-Installation Job Parameter Value

To create an adapter, the post-installation job creates objects—including a Work Area and Program—inside an Adapter Area in an Adapter Domain, and installs the Work Area. These objects are created using the post-installation job parameters values that you entered when you ran the job. If you change the values of some of these parameters after running the job, it may cause problems. The problems vary depending on which parameter you change, and are given for each parameter below.

However, you can call the function FND_PROFILE.SAVE in SQL*Plus to change most parameters. This function takes the following parameters. You must enter single quotes around each value.

  • x_name is the profile name

  • x_value is the profile value that you want to set

  • x_level_name is the name of the level at which the value should be set

Note:

You must set each value at the Site level. To do this, enter 'Site' for the function parameter x_level_name each time you call the function.

To call FND_PROFILE.SAVE:

  1. Log in to SQL*Plus as apps.
  2. At the SQL prompt, enter:
    begin
FND_PROFILE.SAVE ('x_name''x_value' 'x_level_name');
end;
/

You need a line calling FND_PROFILE.SAVE for each post-installation job parameter you need to change. The function parameter values required to change each post-installation parameter are included below. When you are ready to commit the changes, enter:

commit;

The details for each post-installation job parameter are:

  • Object ID Sequence. You cannot change this value.

  • DB Host Name. If the Oracle LSH database moves to a different machine or the name of the current machine changes, you can call FND_PROFILE.SAVE to change the name. However, changing this value will result in subsequent adapter Work Area installations and upgrades failing when you upgrade to a new version of Oracle LSH. Provide the following function parameter values: 

    FND_PROFILE.SAVE('CDR_DBHOST_NAME','New_Host_Name', 'SITE');

  • DB Port Number. If the DB port number changes, you can call FND_PROFILE.SAVE to change it. However, changing this value will result in subsequent adapter Work Area installations and upgrades failing when you upgrade to a new version of Oracle LSH. Provide the following function parameter values: 

    FND_PROFILE.SAVE('CDR_DBPORT_NUM','New_Port_Number', 'SITE');

  • Owning Location. There are currently no restrictions in changing this parameter value. Provide the following function parameter values: 

    FND_PROFILE.SAVE('OWNING_LOCATION','New_Owning_Location', 'SITE');

  • Company ID. Never change the company ID. The company ID is part of the unique key for every object in Oracle LSH, including the adapter objects that were created by running the post-installation job. Changing this value could lead to the system not working in many places, including job execution, the user interface not listing submitted jobs, and more.

Parent topic: Run the Post-Installation Program

Synchronize the APPS Password in OWB

You must synchronize the APPS password in OWB for the Workflow store using the following steps:

  1. Log in to the database as OWBSYS.
  2. Run $CDR_TOP/patch/115/sql/cdrowbpwsynch.sql.
  3. At the prompts, enter the following: Enter the APPS password when prompted by the script.

    • OWB schema name: enter OWBSYS

    • OWB schema password

    • Database name

    • New APPS password

      Note:

      If you change the APPS password after installing Oracle LSH, you must run Autoconfig to create a new .dbc file and do these steps again.

Parent topic: Run the Post-Installation Programs