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

5.14.4 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.
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. 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.

The parameters:

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

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

  • Create 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.

  • Load the predefined Oracle LSH object subtypes.

  • Create 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.

  • Enable 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.)

  • Configure 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.

  • Deploy 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.

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

  1. Click Submit a New Request under one of the following circumstances:

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

    • after following the steps in 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:

    Carefully set the following parameters. You cannot change the values for some of the parameters after you run the job. For details on values you can change, see Change a Post-Installation Job Parameter Value.

    • 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