Installing Objects

You can run the install script to install objects in the imported Domain after you accept an import by committing changes to the target Oracle LSH database instance.

If you ran the import script using COMMIT_ON_NO_ERROR and there were no errors, the import script committed the changes to the database. If you ran the import script set to MANUAL_COMMIT you must commit the changes manually after examining the log file.

The install script accepts the same parameters as the import script. You can also run the install script after upgrading a Domain.

You must have the privileges required to install Oracle LSHWork Areas.

The install script performs the following tasks:

• Installs all the installable Work Areas in the imported Domain. For upgraded Domains, only Work Areas that the import script upgraded or added while upgrading, are installed.
• In all successfully installed Work Areas that include imported objects with backchain Execution Setups, the install script submits these Execution Setups and the jobs run in backchain mode.

  For upgraded Domains, the install script does not submit backchain Execution Setups in the following cases:

  • If the object instance in the upgraded Domain is customized (that is, refers to an object definition outside the Domain)
  • If the source object instance does not contain a backchain Execution Setup but the target object instance does
  • If the source instance's backchain Execution Setup has not been modified since the last import but the target instance has a new backchain Execution Setup
• Writes details of the installation process to domain_name_import.log stored in the database directory.

See "Installation Requirements for Each Object Type" in the Oracle Life Sciences Data Hub Application Developer's Guide for reasons for a Work Area installation to fail.

This section contains the following topic:

• Running the Installation Script
  To run the install script, do the following from the target Oracle Life Sciences Data Hub database instance: