3.1.2 Run Installer

1. Open a command window and browse to <OHI_ROOT>/util/install.
2. Run the installer, either ohi_install.sh or ohi_install.bat. This will assume that the config file ohi_install.cfg is present in the same directory where the installation script located and uses the default configuration from ohi_install.cfg. To specify a different location of ohi_install.cfg or to specify a different environment from ohi_install.cfg, follow the next step.
3. Specify the command line options to specify the location of ohi_install.cfg file and environment to use from ohi_install.cfg.
• Eg: ohi_install.sh  -c  /home/oracle/someLocation/ohi_install.cfg  -e  dev
4. The command line arguments are explained below:

Option		Argument	Description
Short	Long
-c	--cfg	config file path	The location of the configuration file. Default is ohi_install.cfg
-e	--env	environment name	The name that specifies which of the environment settings from the config file to use

3.1.2.1 Install Seed Data

Part of the database objects installation is the installation of Seed Data

3.1.2.1.1 Types of Seed Data

3.1.2.1.1.1 Generic Seed Data

Seed data is maintained by Oracle. Customers should not change this data. It is delivered as part of a release and may be updated by software upgrades.

Tables containing Seed Data include:

3.1.2.1.1.2 Localization Seed Data

This category covers specific data that is required by localizations. The data is maintained by Oracle. There is currently no data in this category. Examples:

• Flex code definitions for a specific page
• Specific messages for localizations.

3.1.2.1.1.3 Sample Data

Sample data is provided by Oracle to give you a headstart during configuration. You can opt to install this data during a fresh install or upgrade. It is not modified during future upgrades. To load sample data, adjust the appropriate parameter in the ohi_install.cfg configuration file. To not load sample data for a certain table, remove the unwanted file from the database/sample_data directory prior to running the install/upgrade process. For more information, see Appendix B - Seed Data.

3.1.2.1.2 Restrictions on using Seed Data

Because Seed Data is maintained by Oracle, it may be modified or even deleted as part of an upgrade. Customers should therefore exercise caution when using seed data in their configuration by abiding these rules.

1. Do not remove (delete) Seed Data rows. A patch may re-insert the row.
2. Do not update columns, other than those indicated as updateble below.
3. Do not make references to rows that may be deleted by Oracle (see table below).

Violations of the rules above (especially rule 3) may lead to failures during the installation of upgrades.

The table below lists the Seed Data tables.

• Data: The table or logical entity
• Updatable columns: The customer may update the values in these columns. They will not be overwritten by upgrade scripts. Other columns should not be updated by the customer.
• Physical Delete: Upgrade scripts may delete this data. The customer should not create references to this data. Example: Do not use OHI messages for your own dynamic checks.

Data	Updatable columns	Physical Delete	Remarks
Access Restrictions		Yes	Also deletes Access Restriction Grants referring to this row
Access Restriction Grants		Yes
Access Roles	ind_enabled	No	Two roles are seeded
Boilerplate Texts		Yes
Countries	all _b columns	No
Country Regions		No
Dynamic Field Usages		No
Dynamic Logic		No
Fields (+ dynamic logic)		No
Flex Codes		No
Flex Code Sets (+ details)		No
Flex Code Systems		No
Languages	ind_default ind_installed	No
Messages	ind_suppress_log_in_ui ind_suppress_log_in_ext ind_mark external_code	Yes
Single Flex Code Definitions (+ usage)		No
Task Types		Yes	Customer is not allowed to change anything in base table
Task Type Attributes	value_char value_number value_datetime value_clob	Yes
Activity Types		Yes	Customer is not allowed to change anything in base table
Users		No	One User will be seeded (system user)