Skip Headers
Oracle® Database Sample Schemas
11g Release 2 (11.2)
E10831-02
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

2 Installation

During a complete installation of your Oracle Database, the sample schemas can be installed automatically with the seed database. If the seed database is removed from the system, you will need to reinstall the sample schemas before you can perform the steps given in the examples that you find in Oracle documentation and training materials.

This chapter describes how to install Sample Schemas. It contains the following sections:

Using the Database Configuration Assistant

When you install Oracle Database with the Oracle Universal Installer, the sample schemas are installed by default if you select the Basic Installation option. Selecting the sample schemas option installs all five schemas (HR, OE, PM, IX, and SH) in the database. If you choose not to install the sample schemas at that time, you can add them later by following the instructions in section "Manually Installing Sample Schemas".

At the end of the installation process, a dialog box displays the accounts that have been created and their lock status. By default, all sample schemas are locked and their passwords are expired. Before you can use a locked account, you must unlock it and reset its password. You can unlock the accounts at this point in the installation process. Alternatively, after the installation completes, you can unlock the schemas and reset their passwords by using the ALTER USER ... ACCOUNT UNLOCK statement. For example:

ALTER USER hr ACCOUNT UNLOCK IDENTIFIED BY Password;

See Also:

"Guidelines for Securing Passwords" in Oracle Database Security Guide for guidelines related to creating secure passwords

The sample schemas available to you depend on the edition of Oracle Database that you have installed and its configuration. Refer to the following table:

Schema Oracle Database Personal edition Oracle Database Standard edition Oracle Database Enterprise edition
HR OK OK OK
OE OK OK OK
PM OK OK OK
IX OK OK OK
SH Not available Not available Needs Partitioning Option installed

Manually Installing Sample Schemas

If you decide not to install the sample schemas at the time of your initial database installation using DBCA, then you can also create the sample schemas manually by running SQL scripts. Install Oracle Database Examples (Companion CD, part of the media kit) to include these scripts in the demo directory under $ORACLE_HOME.


See Also:

Oracle Database Examples Installation Guide for download and installation information

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.

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.


Note:

Make sure that you end the log directory name with a trailing slash, for example, $ORACLE_HOME/demo/schema/log/

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.

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.


See Also:

Guidelines for Installing Sample Schemas before you run oe_main.sql

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

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

Installing the PM Schema

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


See Also:

Guidelines for Installing Sample Schemas before you run pm_main.sql

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

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


Note:

The SQL*Loader data file pm_p_lob.dat contains hard-coded absolute path names that have been set during installation. Before attempting to load the data in a different environment, you should first edit the path names in this file.

Installing the IX Schema

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


See Also:

Guidelines for Installing Sample Schemas before you run ix_main.sql

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

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

Installing the SH Schema

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


See Also:

Guidelines for Installing Sample Schemas before you run sh_main.sql

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


Note:

The dimension tables PROMOTIONS, CUSTOMERS, PRODUCTS and the fact table SALES are loaded by SQL*Loader, after which directory paths are created inside the database to point to the load and log file locations. This allows the loading of the COSTS table by using the external table sales_transactions_ext.

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.

Resetting Sample Schemas

To reset sample schemas to their initial state, use the following syntax from the SQL*Plus command-line interface:

@?/demo/schema/mksample systempwd syspwd hrpwd oepwd pmpwd ixpwd shpwd bipwd default_tablespace temp_tablespace log_file_directory/

The mksample script expects 11 parameters. Provide the password for SYSTEM and SYS, and for the HR, OE, PM, IX, SH, and BI schemas. Specify a temporary and a default tablespace, and make sure to end the name of the log file directory with a trailing slash.

The mksample script produces several log files:

In most situations, there is no difference between installing a Sample Schema for the first time or reinstalling it over a previously installed version. The *_main.sql scripts drop the schema users and all their objects.

In some cases, complex interobject relationships in the OE or IX schemas prevent the DROP USER ... CASCADE operations from completing normally. To correct these rare cases, use one of the following procedures:

For the OC catalog subschema of the OE schema:

  1. Connect as the user OE.

  2. Run the oc_drop.sql. script.

  3. Connect as SYSTEM.

  4. Ensure that no user is connected as OE:

    SELECT username FROM v$session;
    
  5. Drop the user:

    DROP USER oe CASCADE;
    

For the IX schemas:

  1. Connect as SYSTEM.

  2. Ensure that no user is connected as an IX user:

    SELECT username FROM v$session WHERE username like 'IX%';
    
  3. Drop the schemas by running the dix.sql. script. You will be prompted for passwords for the individual users.

Uninstalling Sample Schemas

When you need to remove the Sample Schemas from the installation, you can run the drop_sch.sql on the SQL*Plus command line. Note that this script ships with Oracle Database.

Example 2-1 How to Uninstall Sample Schemas

@?/demo/schema/drop_sch.sql systempwd spool_file_name

The drop_sch.sql script uses two parameters: systempwd is the password for SYSTEM user, and spool_file_name is the name of the spool file that captures the log of the operation.