2 Installation

2.2.1 Schema Dependencies

Various dependencies have been established among the schemas. So, when you create the schemas manually, you must create them in the following order: HR, OE, PM, IX, and SH.

Use this sequence to create the schemas:

1. Create the HR schema.

2. Create the OE schema: The HR schema is already present, and you must know the password for the HR schema to grant HR object privileges to OE. Some HR tables are visible to the OE user with the use of private synonyms. In addition, some OE tables have foreign key relationships to HR tables.

3. Create the PM schema: Foreign key relationships require that the OE schema already exist when the PM schema is created. You must know the password for OE, to grant to PM the right to establish and use these foreign keys.

   Note:

   The PM schema requires the database to be enabled for the Java Virtual Machine (JVM) and interMedia. You can accomplish this during installation or later using the DBCA.

4. Create the IX schema: The information exchange schema IX is based on order entry data in OE. Again, foreign key relationships require that the OE schema already be present when the IX schema is created. You must know the password for OE to grant to IX, the right to establish and use the foreign keys.

5. Create the SH schema. The SH schema logically depends on the OE schema, though you can create this schema without creating the other four schemas.

2.2.2 Guidelines for Installing Sample Schemas

All scripts necessary to install sample schemas reside in $ORACLE_HOME/demo/schema directory. Before you install sample schemas by running these scripts, follow these guidelines:

1. You must connect as a system administrator using the SYSDBA privilege.

2. When prompted to enter a password for the schema, enter a secure password that meets the requirements described in Oracle Database Security Guide.

3. When prompted for tablespace names while running scripts:

   • Enter an appropriate tablespace name, for example, users as the default tablespace for a schema

   • Enter temp as the temporary tablespace for a schema

4. When prompted for the log directory name, enter $ORACLE_HOME/demo/schema/log/ or any other existing directory name.

2.2.3 Installing the HR Schema

All scripts necessary to create the Human Resource (HR) schema reside in $ORACLE_HOME/demo/schema/human_resources.

You need to call only one script, hr_main.sql, to create all the objects and load the data. The following steps provide a summary of the installation process:

1. Log on to SQL*Plus as SYS and connect using the AS SYSDBA privilege.

   sqlplus connect sys as sysdba
   Enter password: password
   
   

2. To run the hr_main.sql script, use the following command:

   SQL> @?/demo/schema/human_resources/hr_main.sql
   
   

3. Enter a secure password for HR

   specify password for HR as parameter 1:
   Enter value for 1:
   
   

   See Also:

   Oracle Database Security Guide for the minimum password requirements

4. Enter an appropriate tablespace, for example, users as the default tablespace for HR

   specify default tablespace for HR as parameter 2:
   Enter value for 2:
   
   

5. Enter temp as the temporary tablespace for HR

   specify temporary tablespace for HR as parameter 3:
   Enter value for 3:
   
   

6. Enter your SYS password

   specify password for SYS as parameter 4:
   Enter value for 4:
   
   

7. Enter the directory path, for example, $ORACLE_HOME/demo/schema/log/, for your log directory

   specify log path as parameter 5:
   Enter value for 5:
   
   

After the hr_main.sql script runs successfully and the HR schema is installed, you are connected as the user HR. To verify that the schema was created, use the following command:

SQL> SELECT       table_name FROM user_tables;

Running hr_main.sql accomplishes the following tasks:

1. Removes any previously installed HR schema

2. Creates the user HR and grants the necessary privileges

3. Connects as HR

4. Calls the scripts that create and populate the schema objects

For a complete listing of the scripts and their functions, refer to Table 5-1.

A pair of optional scripts, hr_dn_c.sql and hr_dn_d.sql, is provided as a schema extension. To prepare the HR schema for use with the directory capabilities of Oracle Internet Directory, run the hr_dn_c.sql script. If you want to return to the initial setup of the HR schema, then use the hr_dn_d.sql script to undo the effects of the hr_dn_c.sql script.

Use the hr_drop.sql script to drop the HR schema.

2.2.4 Installing the OE Schema and Its OC Subschema

All scripts necessary to create the Order Entry (OE) schema and its Online Catalog (OC) subschema reside in $ORACLE_HOME/demo/schema/order_entry.

You need to call only one script, oe_main.sql, to create all the objects and load the data. Running oe_main.sql accomplishes the following tasks:

1. Removes any previously installed OE schema

2. Creates the user OE and grants the necessary privileges

3. Connects as OE

4. Calls the scripts that create and populate the schema objects

After the oe_main.sql script runs successfully and the OE schema is installed, you are connected as the user OE. To verify that the schema was created, use the following command:

SQL> SELECT table_name FROM user_tables;

For a complete listing of the scripts and their functions, refer to Table 5-2.

The oe_drop.sql and oc_drop.sql scripts are used to drop the OE schema and OC subschema, respectively.

2.2.5 Installing the PM Schema

All scripts necessary to create the Product Media (PM) schema reside in $ORACLE_HOME/demo/schema/product_media.

You need to call only one script, pm_main.sql, to create all the objects and load the data. Running pm_main.sql accomplishes the following tasks:

1. Prompts for passwords and tablespace names used within the scripts as well as datafile and log file directories

2. Removes any previously installed PM schema

3. Creates the user PM and grants the necessary privileges

4. Connects as PM

5. Calls the scripts that create and populate the schema objects

After the pm_main.sql script runs successfully and the PM schema is installed, you are connected as the user PM. To verify that the schema was created, use the following command:

SQL> SELECT table_name FROM user_tables;

For a complete listing of the scripts and their functions, refer to Table 5-3 .

The pm_drop.sql script is used to drop the PM schema.

2.2.6 Installing the IX Schema

All scripts necessary to create the Information Exchange (IX) schema reside in $ORACLE_HOME/demo/schema/information_exchange.

To install the Information Exchange (IX) schema, you need to call only one script, ix_main.sql, which creates all the objects and loads the data.

Running ix_main.sql accomplishes the following tasks:

1. Prompts for passwords and tablespace names used within the scripts

2. Removes any previously installed IX schema

3. Creates the user IX and grants the necessary privileges

4. Connects as IX

5. Calls the scripts that create and populate the schema objects

After the ix_main.sql script runs successfully and the IX schema is installed, you are connected as the user IX. To verify that the schema was created, use the following command:

SQL> SELECT table_name FROM user_tables;

For a complete listing of the scripts and their functions, refer to Table 5-4.

The ix_drop.sql script is used for dropping the IX schema.

2.2.7 Installing the SH Schema

All scripts necessary to create the Sales History (SH) schema reside in $ORACLE_HOME/demo/schema/sales_history.

You need to call only one script, sh_main.sql, to create all the objects and load the data. Running sh_main.sql accomplishes the following tasks:

1. Prompts for passwords and tablespace names used within the scripts as well as datafile and log file directories

2. Removes any previously installed SH schema

3. Creates the user SH and grants the necessary privileges

4. Connects as SH

5. Calls the scripts that create and populate the schema objects

After the sh_main.sql script runs successfully and the SH schema is installed, you are connected as the user SH. To verify that the schema was created, use the following command:

SQL> SELECT table_name FROM user_tables;

For a complete listing of the scripts and their functions, refer to Table 5-5.

A pair of optional scripts, sh_olp_c.sql and sh_olp_d.sql, is provided as a schema extension. To prepare the SH schema for use with the advanced analytical capabilities of OLAP Services, run the sh_olp_c.sql create script. If you want to return to the initial setup of the SH schema, then use the script sh_olp_d.sql to undo the effects of sh_olp_c.sql and reinstate dimensions as they were before.

The file used to drop the SH schema is sh_drop.sql.