Oracle® Database

Sample Schemas 11g Release 1 (11.1)
B28328-03

July 2008

Oracle Database Sample Schemas, 11g Release 1 (11.1) B28328-03 Copyright © 2005, 2008, Oracle. All rights reserved. Primary Author: Roza Leyderman Contributing Authors: David Austin , Christian Bauwens, Vimmika Dinesh, Mark Drake, Nancy Greenberg, Deepti Kamal, Diana Lorentz, Nagavalli Pataballa The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

Contents
Preface ................................................................................................................................................................ vii
Audience...................................................................................................................................................... vii Documentation Accessibility .................................................................................................................... vii Related Documents ................................................................................................................................... viii Conventions ............................................................................................................................................... viii

1

Overview
About Sample Schemas........................................................................................................................... 1-1 Oracle Database Sample Schemas Design Principles....................................................................... 1-2 Customer Benefits of Sample Schemas ............................................................................................... 1-2

2

Installation
Using the Database Configuration Assistant ..................................................................................... Manually Installing Sample Schemas.................................................................................................. Schema Dependencies ....................................................................................................................... Guidelines for Installing Sample Schemas ..................................................................................... Installing the HR Schema.................................................................................................................. Installing the OE Schema and Its OC Subschema ......................................................................... Installing the PM Schema.................................................................................................................. Installing the IX Schema.................................................................................................................... Installing the SH Schema .................................................................................................................. Resetting Sample Schemas..................................................................................................................... 2-1 2-2 2-2 2-3 2-3 2-4 2-5 2-5 2-6 2-7

3

Rationale
Overall Description.................................................................................................................................. HR................................................................................................................................................................ OE ............................................................................................................................................................... PM ............................................................................................................................................................... IX.................................................................................................................................................................. SH ............................................................................................................................................................... 3-1 3-1 3-2 3-3 3-3 3-3

4

Schema Diagrams
Sample Schema Diagrams ...................................................................................................................... 4-1

iii

5

Sample Schema Scripts and Object Descriptions
About the Scripts...................................................................................................................................... 5-1 Master Script ............................................................................................................................................. 5-1 mksample.sql ...................................................................................................................................... 5-2 HR Schema ................................................................................................................................................ 5-4 HR Table Descriptions....................................................................................................................... 5-5 OE Schema................................................................................................................................................. 5-7 OE Table Descriptions ....................................................................................................................... 5-8 PM Schema ............................................................................................................................................. 5-10 PM Table Descriptions ................................................................................................................... 5-11 IX Schema ............................................................................................................................................... 5-12 IX Table Descriptions...................................................................................................................... 5-13 SH Schema.............................................................................................................................................. 5-15 SH Table Descriptions .................................................................................................................... 5-15

Index

iv

................................................. 4-3 SH Schema .......................................................List of Figures 4–1 4–2 4–3 HR and OE Schemas.... 4-2 PM Schema....................................................................................................................................................................................................................................... 4-4 v .......................................

.......................................................................................................................................ORDERS Table Description ............................................................... 5-17 SH....... 5-9 OE....................................................................................................................STREAMS_QUEUE_TABLE Table Description ......................................................................................................................... 5-9 OE.....................COUNTRIES Table Description .... 5-7 OE Schema Scripts ........................DEPARTMENTS Table Description..................................................................................... 5-16 SH.................................................................REGIONS Table Description .. 5-11 PM.................................................................................................................................................................................................................................................COUNTRIES Table Description............CUSTOMERS Table Description .........CUSTOMERS Table Description.................................. 5-10 PM Schema Scripts.................................LOCATIONS Table Description .....................PRODUCT_DESCRIPTIONS Table Description.................................. 5-16 SH.................................................................... 5-10 OE.................................................................. 5-6 HR................................................. 5-14 SH Schema Scripts . 5-8 OE.............................................................................................................................. 5-16 SH................................. 5-4 HR Objects .... 5-18 SH...........................JOB_HISTORY Table Description ................................... 5-12 Information Exchange (IX) Schema Scripts.............................................................................................ORDER_ITEMS Table Description ...............................................................................................................................................................TIMES Table Description............................................................... 5-9 OE............... 5-13 IX................................................................ONLINE_MEDIA Table Description ... 5-15 SH Objects .........................................................COSTS Table Description ...List of Tables 5–1 5–2 5–3 5–4 5–5 5–6 5–7 5–8 5–9 5–10 5–11 5–12 5–13 5–14 5–15 5–16 5–17 5–18 5–19 5–20 5–21 5–22 5–23 5–24 5–25 5–26 5–27 5–28 5–29 5–30 5–31 5–32 5–33 5–34 5–35 5–36 HR Schema Scripts..............................................................INVENTORIES Table Description .. 5-6 HR.................................................................. 5-6 HR..............................................ORDERS_QUEUETABLE Table Description.......PROMOTIONS Table Description ........................................................................................................... 5-6 HR.............................................................................................................. 5-6 HR..........................................SALES Table Description .......................................... 5-17 SH.........................................WAREHOUSES Table Description ....................CHANNELS Table Description..................................................................................................................................... 5-9 OE.....EMPLOYEES Table Description ........................................................... 5-11 PM.PRINT_MEDIA Table Description.......................................................... 5-5 HR......................................................... 5-15 SH....................................................................... 5-11 PM Objects ...................... 5-19 vi ......PRODUCTS Table Description.............................................................................................................................................................. 5-10 OE............................... 5-12 IX Objects ........... 5-18 SH................................................................................................................................. 5-5 HR................PRODUCT_INFORMATION Table Description ..........................JOBS Table Description ...................... 5-12 IX......................................................... 5-7 HR Objects .................................................................

com/accessibility/ Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document. services. This documentation is available in HTML format. and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. our documentation includes features that make information available to users of assistive technology. to the disabled community. For more information. and supporting documentation accessible. some screen readers may not always read a line of text that consists solely of a bracket or brace. which is installed when you install the Oracle Database. Accessibility standards will continue to evolve over time.oracle. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites. with good usability. This preface contains the following topics: ■ ■ ■ ■ Audience Documentation Accessibility Related Documents Conventions Audience This document is intended for all users of the seed database. Documentation Accessibility Our goal is to make Oracle products.Preface This guide is a primary source of information on the sample schemas. and contains markup to facilitate access by the disabled community. visit the Oracle Accessibility Program Web site at http://www. vii . however. Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. The conventions for writing code require that closing braces should appear on an otherwise empty line. To that end.

com/ To download free release notes. viii . Monospace type indicates commands within a paragraph. please visit the Oracle Technology Network (OTN). Outside the United States.oracle. text that appears on the screen. or text that you enter.oracle.html Conventions The following text conventions are used in this document: Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action. white papers.com/technology/documentation/index.2398. Related Documents Printed documentation is available for sale in the Oracle Store at http://oraclestore.oracle. emphasis.html If you already have a username and password for OTN. You must register online before using OTN registration is free and can be done at http://www. or other collateral.446.2479. call +1. URLs.com/technology/membership/index. 7 days a week.407. code in examples. For TTY support. installation documentation. or placeholder variables for which you supply particular values. call 800. Italic type indicates book titles. or terms defined in text or the glossary.TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day.458. then you can go directly to the documentation section of the OTN Web site at http://www.

and application demos. As a result. With advances in Oracle Database technology.1 Overview Oracle used the schema SCOTT with its two prominent tables EMP and DEPT for many years. courseware. All Oracle Database documentation and training materials are being converted to Sample Schemas environment as those materials are updated. The Product Media (PM) schema is dedicated to multimedia data types. Order Entry (OE). ■ ■ ■ ■ ■ Overview 1-1 . these tables have become inadequate to show even the most basic features of Oracle Database and other Oracle products. is useful for dealing with matters of intermediate complexity. many other schemas have been created over the years to suit the needs of product documentation. This set of schemas provides a layered approach to complexity: ■ A simple schema Human Resources (HR) is useful for introducing basic topics. The Oracle Database Sample Schemas are a set of interlinked schemas. An extension to this schema provides support for advanced analytic processing. The Online Catalog (OC) subschema is a collection of object-relational database objects built inside the OE schema. software development. A second schema. An extension to this schema supports Oracle Internet Directory demos. A set of schemas gathered under the main schema name Information Exchange (IX) can demonstrate Oracle Advanced Queuing capabilities. This chapter contains the following topics: ■ ■ ■ About Sample Schemas Oracle Database Sample Schemas Design Principles Customer Benefits of Sample Schemas About Sample Schemas The Oracle Database Sample Schemas provide a common platform for examples in each release of the Oracle Database. Many data types are available in this schema. The Sales History (SH) schema is designed to allow for demos with large amounts of data. including nonscalar data types.

When this goal conflicts with the goal of simplicity. schema extensions are used to showcase the trends in focus. When encountering the same set of tables everywhere. This first-hand access to examples facilitates both conceptual understanding and application development. ■ ■ 1-2 Sample Schemas . Relevance for typical users. Through central maintenance and testing of both the creation scripts that build Sample Schemas and the examples that run against the schemas. Sample Schemas provide a logical and physical foundation for adding objects to demonstrate functionality beyond the fundamental scope. The HR and OE schemas are intentionally simple. Quality. Relevance. students. Only the most commonly used database objects are built automatically in the schemas. The base schemas and the extensions bring to the foreground the functionality that customers typically use. Sample Schemas are designed to be applicable to e-business and other significant industry trends (for example. Usability. Rather. they are intended to provide a graduated path from the simple to intermediate levels of database use. ■ ■ ■ Customer Benefits of Sample Schemas Benefits of Sample Schemas are as follows: ■ Continuity of context. the quality of Oracle documentation and training materials is enhanced. The entire set of schemas provides a foundation upon which one can expand to illustrate additional functionality. and developers can spend less time becoming familiar with the schema and more time understanding or explaining the technical concepts. XML). users. Customers can use these schemas in the seed database to run examples that are shown in Oracle documentation and training materials.Oracle Database Sample Schemas Design Principles Oracle Database Sample Schemas Design Principles Sample Schemas have been created and enhanced with the following design principles in mind: ■ Simplicity and ease of use. Extensibility. They will not become overly complex by the addition of features.

If the seed database is removed from the system. OE. Using the Database Configuration Assistant When you install Oracle Database with the Oracle Universal Installer. They are meant to be used for demonstration purposes only. At the end of the installation process. 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. By default. a dialog box displays the accounts that have been created and their lock status. all sample schemas are locked and their Installation 2-1 . PM. the sample schemas can be installed automatically with the seed database. Selecting the sample schemas option installs all five schemas (HR. you can add them later by following the instructions in section "Manually Installing Sample Schemas" on page 2-2. and SH) in the database. If you choose not to install the sample schemas at that time. It contains the following sections: ■ ■ ■ Using the Database Configuration Assistant Manually Installing Sample Schemas Resetting Sample Schemas Caution: By installing any of the Oracle Database Sample Schemas. You should not use Oracle Database Sample Schemas for your personal or business data and applications. This chapter describes how to install Sample Schemas. you will destroy any previously installed schemas that use any of the following user names: ■ ■ ■ ■ ■ HR OE PM SH IX Data contained in any of these schemas will be lost if you run any of the installation scripts described in this section. IX. the sample schemas are installed by default if you select the Basic Installation option.2 Installation During a complete installation of your Oracle Database.

Manually Installing Sample Schemas passwords are expired. Refer to the following table: Oracle Database Personal edition OK OK OK OK Not available Oracle Database Standard edition OK OK OK OK Not available Oracle Database Enterprise edition OK OK OK OK Needs Partitioning Option installed Schema HR OE PM IX SH Manually Installing Sample Schemas If you decide not to install the sample schemas at the time of your initial database installation using DBCA. Install Oracle Database Examples (Companion CD. IX. ACCOUNT UNLOCK statement. 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. Some HR tables are visible to the OE user with the use of private synonyms. See Also: Oracle Database Examples Installation Guide for download and installation information Schema Dependencies Various dependencies have been established among the schemas. OE. In addition. You can accomplish this during installation or later using the DBCA. For example: ALTER USER hr ACCOUNT UNLOCK IDENTIFIED BY Password.. Create the PM schema: Foreign key relationships require that the OE schema already exist when the PM schema is created. you can unlock the schemas and reset their passwords by using the ALTER USER . Before you can use a locked account. You can unlock the accounts at this point in the installation process. some OE tables have foreign key relationships to HR tables. and SH. you must unlock it and reset its password. Create the HR schema. 2-2 Sample Schemas . You must know the password for OE. So. then you can also create the sample schemas manually by running SQL scripts. to grant to PM the right to establish and use these foreign keys. Create the OE schema: The HR schema is already present. after the installation completes. 3.. Note: The PM schema requires the database to be enabled for the Java Virtual Machine (JVM) and interMedia. 2. part of the media kit) to include these scripts in the demo directory under $ORACLE_HOME. Use this sequence to create the schemas: 1. PM. you must create them in the following order: HR. and you must know the password for the HR schema to grant HR object privileges to OE. when you create the schemas manually. Alternatively.

sql 3. You must connect as a system administrator using the SYSDBA privilege. 5. enter a secure password that meets the requirements described in Oracle Database Security Guide. When prompted to enter a password for the schema. 3. hr_main. enter $ORACLE_ HOME/demo/schema/log/ or any other existing directory name.Manually Installing Sample Schemas 4. 2. Note: Make sure that you end the log directory name with a trailing slash. for example. The SH schema logically depends on the OE schema. Before you install sample schemas by running these scripts. To run the hr_main. for example. 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. The following steps provide a summary of the installation process: 1. You need to call only one script. Again. users as the default tablespace for HR specify default tablespace for HR as parameter 2: Installation 2-3 . sqlplus connect sys as sysdba Enter password: password 2. Guidelines for Installing Sample Schemas All scripts necessary to install sample schemas reside in $ORACLE_ HOME/demo/schema directory. $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. Create the SH schema. for example. Create the IX schema: The information exchange schema IX is based on order entry data in OE. the right to establish and use the foreign keys. follow these guidelines: 1. foreign key relationships require that the OE schema already be present when the IX schema is created. When prompted for the log directory name. though you can create this schema without creating the other four schemas. to create all the objects and load the data.sql. Log on to SQL*Plus as SYS and connect using the AS SYSDBA privilege. users as the default tablespace for a schema Enter temp as the temporary tablespace for a schema ■ 4. use the following command: SQL> @?/demo/schema/human_resources/hr_main.sql script. Enter an appropriate tablespace. You must know the password for OE to grant to IX. When prompted for tablespace names while running scripts: ■ Enter an appropriate tablespace name.

is provided as a schema extension.sql and hr_dn_d. 2. Running oe_main.sql script.sql You need to call only one script. Removes any previously installed HR schema Creates the user HR and grants the necessary privileges Connects as HR Calls the scripts that create and populate the schema objects For a complete listing of the scripts and their functions. Removes any previously installed OE schema Creates the user OE and grants the necessary privileges Connects as OE Calls the scripts that create and populate the schema objects 2-4 Sample Schemas . use the following command: SQL> SELECT table_name FROM user_tables. for your log directory specify log path as parameter 5: Enter value for 5: After the hr_main. To prepare the HR schema for use with the directory capabilities of Oracle Internet Directory. then use the hr_dn_d. See Also: Guidelines for Installing Sample Schemas before you run oe_main. you are connected as the user HR. 4. run the hr_dn_c. Enter the directory path.Manually Installing Sample Schemas Enter value for 2: 5. Running hr_main. Enter temp as the temporary tablespace for HR specify temporary tablespace for HR as parameter 3: Enter value for 3: 6.sql.sql script runs successfully and the HR schema is installed. Enter your SYS password specify password for SYS as parameter 4: Enter value for 4: 7. 3. to create all the objects and load the data. refer to Table 5–1 on page 5-4.sql.sql script to drop the HR schema. To verify that the schema was created. A pair of optional scripts. 4. for example.sql accomplishes the following tasks: 1.sql script to undo the effects of the hr_dn_c. If you want to return to the initial setup of the HR schema.sql accomplishes the following tasks: 1.sql script. 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. oe_main. hr_dn_c. Use the hr_drop. 2. 3. $ORACLE_HOME/demo/schema/log/.

Before attempting to load the data in a different environment. Prompts for passwords and tablespace names used within the scripts as well as datafile and log file directories Removes any previously installed PM schema Creates the user PM and grants the necessary privileges Connects as PM Calls the scripts that create and populate the schema objects After the pm_main.Manually Installing Sample Schemas After the oe_main. use the following command: SQL> SELECT table_name FROM user_tables. refer to Table 5–10 on page 5-7. you should first edit the path names in this file. you are connected as the user OE.sql script is used to drop the PM schema.sql To install the Information Exchange (IX) schema. respectively. pm_main. To verify that the schema was created. The pm_drop. you need to call only one script. to create all the objects and load the data. The oe_drop. Note: The SQL*Loader data file pm_p_lob.sql scripts are used to drop the OE schema and OC subschema.sql script runs successfully and the OE schema is installed. For a complete listing of the scripts and their functions. you are connected as the user PM. Installation 2-5 . 3. 4. ix_ main. To verify that the schema was created. See Also: Guidelines for Installing Sample Schemas before you run pm_main.sql and oc_drop. Installing the PM Schema All scripts necessary to create the Product Media (PM) schema reside in $ORACLE_ HOME/demo/schema/product_media. 5. 2. For a complete listing of the scripts and their functions.dat contains hard-coded absolute path names that have been set during installation.sql. See Also: Guidelines for Installing Sample Schemas before you run ix_main.sql.sql You need to call only one script. use the following command: SQL> SELECT table_name FROM user_tables. Installing the IX Schema All scripts necessary to create the Information Exchange (IX) schema reside in $ORACLE_HOME/demo/schema/information_exchange. which creates all the objects and loads the data. Running pm_main. refer to Table 5–19 on page 5-11.sql accomplishes the following tasks: 1.sql script runs successfully and the PM schema is installed.

To verify that the schema was created. Prompts for passwords and tablespace names used within the scripts as well as datafile and log file directories Removes any previously installed SH schema Creates the user SH and grants the necessary privileges Connects as SH Calls the scripts that create and populate the schema objects After the sh_main. Installing the SH Schema All scripts necessary to create the Sales History (SH) schema reside in $ORACLE_ HOME/demo/schema/sales_history. you are connected as the user SH. 2.sql script runs successfully and the IX schema is installed. sh_main. This allows the loading of the COSTS table by using the external table sales_transactions_ ext. 3. 3. Note: The dimension tables PROMOTIONS.sql script is used for dropping the IX schema.sql accomplishes the following tasks: 1. For a complete listing of the scripts and their functions. Prompts for passwords and tablespace names used within the scripts Removes any previously installed IX schema Creates the user IX and grants the necessary privileges Connects as IX Calls the scripts that create and populate the schema objects After the ix_main. use the following command: SQL> SELECT table_name FROM user_tables. 5. to create all the objects and load the data. after which directory paths are created inside the database to point to the load and log file locations. 4. 4. 2.sql You need to call only one script. PRODUCTS and the fact table SALES are loaded by SQL*Loader. CUSTOMERS.sql script runs successfully and the SH schema is installed. you are connected as the user IX. The ix_drop. 2-6 Sample Schemas . Running sh_main.Manually Installing Sample Schemas Running ix_main. See Also: Guidelines for Installing Sample Schemas before you run sh_main.sql accomplishes the following tasks: 1. refer to Table 5–23 on page 5-12.sql. 5. To verify that the schema was created. For a complete listing of the scripts and their functions. use the following command: SQL> SELECT table_name FROM user_tables. refer to Table 5–27 on page 5-15.

log is the Sample Schema creation log file. CASCADE operations from completing normally. 4. promo. prod.sql create script. oe_oc_main.sql scripts drop the schema users and all their objects. OE. Connect as the user OE.sql and reinstate dimensions as they were before.sql. complex interobject relationships in the OE or IX schemas prevent the DROP USER . sales_ext.log is the SH schema creation log file.COSTS. SH. The *_main.log is the SQL*Loader log file for SH.sql.PRINT_MEDIA. 3. In some cases. use one of the following procedures: For the OC catalog subschema of the OE schema: 1. hr_main.SALES. and for the HR.log is the SQL*Loader log file for SH.PRODUCTS. script. 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.CUSTOMERS. is provided as a schema extension. ix_main. Installation 2-7 . Connect as SYSTEM. To correct these rare cases. Provide the password for SYSTEM and SYS. sh_olp_c. and BI schemas. Specify a temporary and a default tablespace. To prepare the SH schema for use with the advanced analytical capabilities of OLAP Services. there is no difference between installing a Sample Schema for the first time or reinstalling it over a previously installed version. Run the oc_drop.sql to undo the effects of sh_olp_c.log is the IX schema creation log file.log is the HR schema creation log file.log is the SQL*Loader log file for SH. If you want to return to the initial setup of the SH schema.sql.. IX. then use the script sh_olp_d. run the sh_olp_c. sh_main.log is the PM schema creation log file. pm_p_lob. Ensure that no user is connected as OE: SELECT username FROM v$session. Resetting Sample Schemas To reset sample schemas to their initial state. sales.PROMOTIONS.log is the SQL*Loader log file for PM. PM. pm_main. cust.log is the external table log file for SH. 2.log is the OE schema creation log file. The mksample script produces several log files: ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ ■ mkverify..Resetting Sample Schemas A pair of optional scripts.sql and sh_olp_d. In most situations. The file used to drop the SH schema is sh_drop.log is the SQL*Loader log file for SH. and make sure to end the name of the log file directory with a trailing slash.

You will be prompted for passwords for the individual users. Drop the user: DROP USER oe CASCADE. For the IX schemas: 1. 2. 3. script. Connect as SYSTEM. 2-8 Sample Schemas .sql. Ensure that no user is connected as an IX user: SELECT username FROM v$session WHERE username like 'IX%'.Resetting Sample Schemas 5. Drop the schemas by running the dix.

salary. e-mail address. each employee has an identification number. and the department are recorded. The company also tracks information about jobs within the organization. job identification code. The company has several divisions: ■ The Human Resources division tracks information about the employees and the facilities. The Order Entry division tracks product inventories and sales of company’s products through various channels. When an employee resigns. and manager. The Sales division tracks business statistics to facilitate business decisions. Each job has an identification code.3 Rationale The Oracle Database sample schemas are based on a fictitious company that sells goods through various channels. Some employees have been with the company for a long time and have held different positions within the company. the duration the employee was working. job title. ■ ■ ■ ■ Each of these divisions is represented by a schema. and a minimum and maximum salary range for the job. HR In the Human Resource (HR) records. Some employees earn commissions in addition to their salary. Rationale 3-1 . the job identification number. The Information Exchange division manages shipping through B2B applications. The Product Media division maintains descriptions and detailed information about each product sold by the company. This chapter describes the fictitious company and contains the following sections: ■ ■ ■ ■ ■ ■ Overall Description HR OE PM IX SH Overall Description The sample company portrayed by the Oracle Database Sample Schemas operates worldwide to fill orders for several products.

such as computer hardware and software. country. the unit price. and the sales representative who helped place the order. where month is a three-letter month abbreviation (for example. city. and tools. currency name. Customer information is also tracked. a minimum price at which a product will be sold. Jan. and postal code. by querying public views RESOURCE_VIEW and PATH_VIEW. Customer records include customer name. When a customer places an order.OE The sample company is regionally diverse. The company maintains information about these products. Some customers place orders through the Internet. Each warehouse has a warehouse identification number. Inventory information is also recorded for all products. The purchase order XML documents are located in the Oracle XML DB Repository folder $ORACLE_HOME/rdbms/demo/order_entry/2002/month. clothing. the company records details such as the country name. Some customers have an account manager. and a URL address for manufacturer information. including the warehouse where the product is available and the quantity on hand. In places where the departments and warehouses are located. the category into which the product falls. the company tracks the date of the order. the current status of the order. name. a list price. the company also tracks the number of items ordered. and location identification number. such as by querying the PURCHASEORDER object-relational table by using SQL. The company maintains warehouses in several locations to fulfill customer needs. and the country code. 3-2 Sample Schemas . how the order was placed. Each customer has an identification number. total amount of the order. and this information is also recorded. and so on). If an order is placed over the Internet. the warranty period if applicable. Because of language differences among customers. so e-mail addresses are also recorded. You can access these documents in various ways. currency symbol. Because products are sold worldwide. order entry (OE). the company records the native language and territory of each customer. and the products ordered. Mar. postal code. state or province. the availability status of the product. Each department is associated with one location. Feb. to limit the amount of products they can purchase at one time. and by querying the repository using XPath expressions. shipping mode. city or province.xsd. The XML documents are stored in the Oracle XML DB Repository after validation against the registered XML schema purchaseorder. music. such as product identification numbers. no sales representative is recorded. The OE schema also contains XML purchase order documents. and each department is identified either by a unique department number or a short name. Each employee is assigned to a department. the supplier. and each location has a full address that includes the street name. facility description. OE The company sells several products. The sales representative may or may not be the same person as the account manager for a customer. the company maintains the names of the products and their descriptions in several languages. street name. and the region where the country is located geographically. phone numbers (up to five phone numbers for each customer). The company places a credit limit on its customers. In addition to order information. the weight group (for shipping purposes). so it tracks the locations of its warehouses and departments.

The same customers and products are used in OC as in the OE schema proper. where users navigate to specific products by drilling down through increasingly specialized categories of products. After the orders are either shipped or back ordered. the company intends to expand beyond its current in-house distribution system to a system that will allow other businesses to provide the shipping. Many of these reports are time-based and nonvolatile. but the OC subschema organizes the products into a hierarchy of parent categories and subcategories. depending on the location of the customer.SH OC Description The Online Catalog (OC) subschema of the OE schema addresses an online catalog merchandising scenario. The company loads data into its data warehouse regularly to gather statistics for these reports. the company uses a database server and an application server. That is. To demonstrate connectivity from outside the firewall. SH The sample company does a high volume of business. and both Advanced Queueing Servlet and Oracle Internet Directory provide the required routing between the queues. The Information Exchange (IX) schema stores such information. Eventually. The new order application directly enables a queue. It is important that the message be delivered only once and that there be a system for tracking and reviewing messages to facilitate resolution of any discrepancies with the order. The Product Media (PM) schema is used to store such information. PM The company stores multimedia and print information about its products in a database. For the purpose of this test application. The application provides a mechanism for examining the XML messages as well as monitoring the queues. a message must be sent back to the employee concerned to inform about the status of the order and to initiate the billing. both the generation of a new order and customer service reporting are performed using queues. so it runs business statistics reports to aid in decision making. XML is the perfect format for sending messages. Examples of such information are: ■ ■ ■ ■ ■ Promotional audio and video clips Product images and thumbnails for Web publishing Press release texts Print media advertisements Other promotional texts and translations IX The company has decided to test the use of messaging to manage its proposed B2B applications. they analyze past data trends. This hierarchy corresponds to the arrangement on an e-commerce portal site. Then. while the customer service queries require XML messaging to disable a queue. These reports include Rationale 3-3 . The messages sent must be in a self-contained format. the order is routed to the nearest region for shipping. The plan calls for a small test that will allow a user from outside the firewall to place an order and track its status. The order must be booked into the main system.

When the company runs special promotions on its products. 3-4 Sample Schemas . monthly.SH annual. quarterly. It also analyzes sales by geographical area. The company also runs reports on distribution channels through which its sales are delivered. These reports are stored with the help of Sales History (SH) schema. it analyzes the impact of the promotions on sales. and weekly sales figures by product.

Schema Diagrams 4-1 . Note that the scripts and table descriptions for these two schemas are in section "HR Schema" on page 5-4 and "OE Schema" on page 5-7. respectively. Figure 4–2. "PM Schema" on page 4-3 illustrates the PM schema.4 Schema Diagrams This chapter contains diagrams of sample schemas. "HR and OE Schemas" on page 4-2. but its scripts and table description are in section "IX Schema" on page 5-12. Note that the scripts and table description for the PM schema are at "PM Schema" on page 5-10. "SH Schema" on page 4-4 illustrates the SH schema. illustrates HR and OE schemas and their relationship. Sample Schema Diagrams Figure 4–1. Figure 4–3. This edition of the book does not illustrate the IX schema. Note that the scripts and table description for the SH schema are in section "SH Schema" on page 5-15.

Sample Schema Diagrams Figure 4–1 HR and OE Schemas 4-2 Sample Schemas .

Sample Schema Diagrams Figure 4–2 PM Schema Schema Diagrams 4-3 .

Sample Schema Diagrams Figure 4–3 SH Schema 4-4 Sample Schemas .

Sample Schema Scripts and Object Descriptions 5-1 .sql script. ■ Sample Schemas script directories are located in the $ORACLE_HOME/demo/schema directory after completing the Oracle Database Examples installation. Master Script The master script. This main script calls all other scripts necessary to build and load the schema.sql.5 Sample Schema Scripts and Object Descriptions This chapter describes the scripts used to generate the Oracle Database Sample Schemas. where xx is the schema abbreviation. You must install the Oracle Database Examples media to populate the directories with the Sample Schema scripts. removes all objects from a particular schema.sql. It contains the following sections: ■ ■ ■ ■ ■ ■ ■ About the Scripts Master Script HR Schema OE Schema PM Schema IX Schema SH Schema About the Scripts Sample Schemas script directories are located in $ORACLE_HOME/demo/schema. It does not include the scripts for the individual schemas because these scripts are very lengthy. where xx is the schema abbreviation. Each schema has two primary scripts: ■ The xx_main. sets up the overall Sample Schema environment and creates all the schemas. mksample. Note: This chapter contains only the master script for the entire sample schemas environment. resets and creates all objects and data for a particular schema. The script xx_drop.

sql.BI . These variables are instantiated on installation.CAUTION: This script will erase the following schemas: .creates all 5 Sample Schemas DESCRIPTION This script rees and creates all Schemas belonging to the Oracle Database 10g Sample Schemas. Oracle Corporation.OE .sbs 02-apr-2003.USAGE: To return the Sample Schemas to their initial state.PM . NAME mksample.SH . The instantiated scripts matches the directory structure on your system . please use the Database Configuration Assistant DBCA to configure the Sample Schemas.CAUTION: Never use the preceding Sample Schemas for anything other than demos and examples . and %s_ shPath%.HR . mksample. 2003.sql The text of the mksample. .sql .IX .sql script follows: Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem Rem $Header: mksample. you will notice variables such as %s_pmPath%. SYSTEM and the schemas as parameters.14:55:17 $ mksample. NOTES .sql. %s_logPath%.Tablespace EXAMPLE created with: CREATE TABLESPACE example NOLOGGING DATAFILE '<filename>' SIZE 150M REUSE AUTOEXTEND ON NEXT 640k MAXSIZE UNLIMITED EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO. you can call this script and pass the passwords for SYS. which follows.Master Script Note: In the master script (mksample. Example: @?/demo/schema/mksample mgr secure h1 o2 p3 q4 s5 (please choose your own passwords for security purposes) MODIFIED (MM/DD/YY) SET FEEDBACK 1 SET NUMWIDTH 10 5-2 Sample Schemas .OUI instantiates this script during install and saves it as mksample. If you are unsure about the prerequisites for the Sample Schemas.sql). All rights reserved.sql Copyright (c) 2001.

Master Script SET SET SET SET SET SET SET LINESIZE 80 TRIMSPOOL ON TAB OFF PAGESIZE 999 ECHO OFF CONCAT '. CASCADE.. CASCADE..' SHOWMODE OFF PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT DEFINE PROMPT PROMPT 11: DEFINE PROMPT PROMPT PROMPT DEFINE specify password for SYSTEM as parameter 1: password_system = &1 specify password for SYS as parameter 2: password_sys = &2 specify password for HR as parameter 3: password_hr = &3 specify password for OE as parameter 4: password_oe = &4 specify password for PM as parameter 5: password_pm = &5 specify password for IX as parameter 6: password_ix = &6 specify password for SH as parameter 7: password_sh = &7 specify password for BI as parameter 8: password_bi = &8 specify default tablespace as parameter 9: default_ts = &9 specify temporary tablespace as parameter 10: temp_ts = &10 specify log file directory (including trailing delimiter) as parameter logfile_dir = &11 Sample Schemas are being created . CASCADE. CONNECT system/&&password_system SET SHOWMODE OFF Sample Schema Scripts and Object Descriptions 5-3 . CASCADE. vrs = v3 CONNECT system/&&password_system DROP DROP DROP DROP DROP DROP USER USER USER USER USER USER hr oe pm ix sh bi CASCADE. CASCADE.

sql &&password_pm &&default_ts &&temp_ts &&password_oe &&password_sys %s_pmPath% &&logfile_dir %s_pmPath% CONNECT system/&&password_system SET SHOWMODE OFF @?/demo/schema/info_exchange/ix_main.sql &&password_oe &&default_ts &&temp_ts &&password_hr &&password_sys %s_oePath% &&logfile_dir &vrs CONNECT system/&&password_system SET SHOWMODE OFF @?/demo/schema/product_media/pm_main.sql hr_code.sql &&password_hr &&default_ts &&temp_ts &&password_sys &&logfile_dir CONNECT system/&&password_system SET SHOWMODE OFF @?/demo/schema/order_entry/oe_main.sql &&password_ix &&default_ts &&temp_ts &&password_sys &&logfile_dir &vrs CONNECT system/&&password_system SET SHOWMODE OFF @?/demo/schema/sales_history/sh_main &&password_sh &&default_ts &&temp_ts &&password_sys %s_shPath% &&logfile_dir &vrs CONNECT system/&&password_system SET SHOWMODE OFF @?/demo/schema/bus_intelligence/bi_main &&password_bi &&default_ts &&temp_ts &&password_sys &&password_oe &&password_sh &&logfile_dir &vrs CONNECT system/&&password_system SPOOL OFF DEFINE veri_spool = &&logfile_dir.sql 5-4 Sample Schemas .sql hr_cre. Table 5–1 on page 5-4 lists the HR scripts in alphabetical order.sql hr_comnt. while Table 5–2 on page 5-5 lists its objects.log @?/demo/schema/mkverify &&password_system &veri_spool EXIT HR Schema This section lists the names of the scripts that create the human resources (HR) schema and describes the objects in the schema.HR Schema @?/demo/schema/human_resources/hr_main..mkverify_&vrs. Table 5–1 HR Schema Scripts Description Collects statistics on the tables in the schema Creates procedural objects in the schema Creates comments for each object in the schema Creates the HR objects Script Name hr_analz.

UPDATE_JOB_HISTORY EMP_DETAILS_VIEW Procedure Sequence Table Trigger View HR Table Descriptions This section describes the columns of each table of the HR schema. " HR.DEPARTMENTS Table Description" on page 5-6 Table 5–5.LOCATIONS Table Description" on page 5-6 Table 5–9. LOC_STATE_PROVINCE_IX.HR Schema Table 5–1 (Cont. EMP_EMP_ID_PK. " HR. calls other scripts Populates the objects Table 5–2 Object Type Index HR Objects Objects COUNTRY_C_ID_PK. LOC_ CITY_IX.REGIONS Table Description" on page 5-7 HR.sql hr_popul. JOB_ID_PK.EMPLOYEES Table Description" on page 5-6 Table 5–6. EMPLOYEES_SEQ. LOCATIONS. EMP_ MANAGER_IX. " HR.sql hr_drop. JOBS.COUNTRIES Table Description" on page 5-5 Table 5–4. LOC_COUNTRY_IX. SECURE_DML DEPARTMENTS_SEQ. EMP_ DEPARTMENT_IX.sql hr_dn_d. " HR. LOC_ID_PK. JHIST_JOB_IX. JOB_HISTORY. EMP_NAME_IX. DEPT_ID_PK. JHIST_EMPLOYEE_ IX. REGIONS SECURE_EMPLOYEES.JOB_HISTORY Table Description" on page 5-6 Table 5–8. JHIST_DEPARTMENT_IX. REG_ID_PK ADD_JOB_HISTORY.JOBS Table Description" on page 5-6 Table 5–7. JHIST_EMP_ID_ST_DATE_PK. " HR.sql hr_idx. EMPLOYEES.sql Description Adds the distinguished name column used by Oracle Internet Directory to the employees and departments tables Drops the Oracle Internet Directory distinguished name column from employees and departments Drops the HR schema and all its objects Creates indexes on the HR tables Main script for the HR schema. " HR. LOCATIONS_SEQ COUNTRIES. " HR. as follows: ■ ■ ■ ■ ■ ■ ■ Table 5–3.) HR Schema Scripts Script Name hr_dn_c. EMP_JOB_IX.COUNTRIES Table Description Null? NOT NULL Type CHAR(2) VARCHAR2(40) NUMBER Table 5–3 Column Name COUNTRY_ID COUNTRY_NAME REGION_ID Sample Schema Scripts and Object Descriptions 5-5 . DEPARTMENTS. EMP_EMAIL_UK.sql hr_main. DEPT_LOCATION_IX.

2) NUMBER(2.2) NUMBER(6) NUMBER(4) Column Name EMPLOYEE_ID FIRST_NAME LAST_NAME EMAIL PHONE_NUMBER HIRE_DATE JOB_ID SALARY COMMISSION_PCT MANAGER_ID DEPARTMENT_ID Table 5–6 HR.EMPLOYEES Table Description Null? NOT NULL Type NUMBER(6) VARCHAR2(20) NOT NULL NOT NULL VARCHAR2(25) VARCHAR2(20) VARCHAR2(20) NOT NULL NOT NULL DATE VARCHAR2(10) NUMBER(8.LOCATIONS Table Description Null? NOT NULL Type NUMBER(4) Column Name LOCATION_ID 5-6 Sample Schemas .JOB_HISTORY Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL Type NUMBER(6) DATE DATE VARCHAR2(10) NUMBER(4) Column Name EMPLOYEE_ID START_DATE END_DATE JOB_ID DEPARTMENT_ID Table 5–8 HR.JOBS Table Description Null? NOT NULL NOT NULL Type VARCHAR2(10) VARCHAR2(35) NUMBER(6) NUMBER(6) Column Name JOB_ID JOB_TITLE MIN_SALARY MAX_SALARY Table 5–7 HR.DEPARTMENTS Table Description Null? NOT NULL NOT NULL Type NUMBER(4) VARCHAR2(30) NUMBER(6) NUMBER(4) Column Name DEPARTMENT_ID DEPARTMENT_NAME MANAGER_ID LOCATION_ID Table 5–5 HR.HR Schema Table 5–4 HR.

oe_p_hu.sql.sql.sql.sql. oe_p_pt.sql.sql.sql.sql.sql oc_cre.sql.sql.sql.sql.sql. oe_p_zht.sql oe_main.LOCATIONS Table Description Column Name STREET_ADDRESS POSTAL_CODE CITY STATE_PROVINCE COUNTRY_ID NOT NULL Null? Type VARCHAR2(40) VARCHAR2(12) VARCHAR2(30) VARCHAR2(25) CHAR(2) Table 5–9 HR.sql oe_idx. oe_p_ pl.sql. oe_p_f. oe_p_d.sql. oe_p_ko.sql oe_comnt. oe_p_sf. oe_p_nl. oe_p_frc. oe_p_n. oe_p_cs. Note that language-specific statements for product names and descriptions are stored in these files (each representing a different language): INSERToe_p_us.sql oc_main. oe_p_th.sql. oe_p_dk. oe_p_ja. Table 5–10 on page 5-7 lists the OE scripts in alphabetical order.sql a OE Schema Scripts Description Adds comments to the online catalog (OC) subschema wherever possible Creates the OC subschema Drops the OC subschema Main script for the OC subschema Populates the object tables Gathers statistics on the OE objects Creates comments for the objects in the schema Creates the OE objects Drops the OE schema and all its objects Creates indexes on the OE tables Main script for the OE schema.sql oe_views.sql. oe_p_ iw.sql.sql.sql oe_analz. oe_p_ zhs.sqloe_p_ar.REGIONS Table Description Null? NOT NULL Type NUMBER VARCHAR2(25) Column Name REGION_ID REGION_NAME OE Schema This section lists the names of the scripts that create the Order Entry (OE) schema and describes the objects in the schema. oe_p_ptb. Table 5–10 Script Name oc_comnt.sql.sql oc_drop. oe_p_ s.sql.sql oe_drop.sql.) HR.sql.sql oc_popul.sql. oe_p_ro.sql.sql.sql oe_cre. oe_p_tr. oe_p_sk.sql. while Table 5–11 on page 5-8 lists its objects. oe_p_e. oe_p_ esa. calls other scripts Creates the OE schema views Sample Schema Scripts and Object Descriptions 5-7 .OE Schema Table 5–8 (Cont.sql. oe_p_el. oe_p_ru. oe_p_i.

PRODUCT_INFORMATION Table Description" on page 5-10 Table 5–18. SYS_C003590. SYS_ LOB0000046019C00011$$. CORPORATE_ CUSTOMER_TYP. SYDNEY_INVENTORY. SYS_C003588. XDBPO_ACTION_TYPE. LEAF_CATEGORY_TYP ACCOUNT_MANAGERS. WAREHOUSE_TYP. COMPOSITE_CATEGORY_TYP. PRODUCT_INFORMATION_PK. PRODUCT_INFORMATION. INVENTORY_LIST_ TYP. ORDER_TYP. " OE. INVENTORY_TYP. " OE. XDBPO_LINEITEM_ COLLECTION. ORD_ORDER_DATE_IX. SUBCATEGORY_ REF_LIST_TYP.CUSTOMERS Table Description" on page 5-9 Table 5–13. SYS_C003589. INV_PRODUCT_IX. ORDERS_VIEW. SYS_YOID0000046075$. INVENTORIES. DEPTVIEW. ORDER_ITEMS_ UK. " OE. SYS_LOB0000046019C00024$$. WAREHOUSES_PK. ORDERS. SYS_ YOID0000046077$. XDBPO_TYPE CATALOG_TYP. BOMBAY_INVENTORY. ORDERS_ITEMS_TRG. XDBPO_ACTIONS_TYPE. JOBS. SYS_ C003584. ORDER_ITEM_TYP. ITEM_ORDER_IX. SYS_ LOB0000046044C00003$$ COUNTRIES. SYS_LOB0000046019C00012$$. JOB_HISTORY. OC_CUSTOMERS. SYS_LOB0000045852C00012$$. " OE. WHS_LOCATION_IX GET_PHONE_NUMBER_F ORDERS_SEQ SYS_LOB0000045843C00022$$. CUST_ LNAME_IX. PHONE_LIST_TYP. SYS_ LOB0000046019C00005$$. ORD_CUSTOMER_IX. CUSTOMERS_VIEW. ORDERS_TRG CATALOG_TYP. WAREHOUSES INSERT_ORD_LINE. SYS_LOB0000046019C00007$$. PRD_DESC_PK. LEAF_CATEGORY_TYP. ITEM_PRODUCT_IX. XDBPO_PART_TYPE. SYS_ LOB0000045852C00013$$. REFERENCE_IS_UNIQUE.INVENTORIES Table Description" on page 5-9 Table 5–14. CUST_UPPER_NAME_IX. SYS_YOID0000046073$. CUSTOMER_TYP. PRODUCT_ DESCRIPTIONS. PROD_NAME_IX. CUST_ACCOUNT_MANAGER_IX. INVENTORY_IX. SYS_YOID0000046079$. CUST_ADDRESS_TYP.ORDER_ITEMS Table Description" on page 5-9 Table 5–16. OC_INVENTORIES. ORDER_PK. as follows: ■ ■ ■ ■ ■ ■ ■ Table 5–12. XDBPO_ACTION_COLLECTION. ORDER_LIST_TYP. XDBPO_LINEITEMS_TYPE. LOCATIONS CUSTOMERS. SYS_YOID0000046081$.PRODUCT_DESCRIPTIONS Table Description" on page 5-10 Table 5–17. SYS_LOB0000046019C00032$$. " OE. ORD_SALES_ REP_IX. OC_ ORDERS. SYS_ LOB0000046019C00015$$. PRODUCTS. SYS_ LOB0000046019C00031$$. TORONTO_INVENTORY Function Sequence Lob Synonym Table Trigger Type Type Body View OE Table Descriptions This section describes the columns of each table of the OE schema. XDBPO_SHIPINSTRUCTIONS_TYPE. " OE. " OE. ORDER_ITEMS. ORDER_ITEMS_PK. CATEGORY_TYP. PROMO_ID_PK. DEPARTMENTS.WAREHOUSES Table Description" on page 5-10 5-8 Sample Schemas . SYS_LOB0000046019C00004$$. ORDER_ITEM_LIST_TYP. OC_PRODUCT_INFORMATION. PRODUCT_REF_LIST_TYP. XDBPO_ REJECTION_TYPE. PRODUCT_PRICES. SYS_ LOB0000045852C00003$$. CUST_EMAIL_IX. PROD_SUPPLIER_IX. COMPOSITE_CATEGORY_TYP. SYS_C003587. EMPLOYEES. OC_CORPORATE_CUSTOMERS. PRODUCT_INFORMATION_TYP.ORDERS Table Description" on page 5-9 Table 5–15.OE Schema Table 5–11 Object Type Index HR Objects Objects CUSTOMERS_PK. SYS_LOB0000045843C00023$$. XDBPO_LINEITEM_TYPE.

ORDER_ITEMS Table Description Null? NOT NULL Type NUMBER(12) Column Name ORDER_ID Sample Schema Scripts and Object Descriptions 5-9 .ORDERS Table Description Null? NOT NULL NOT NULL Type NUMBER(12) TIMESTAMP(6) WITH LOCAL TIME ZONE VARCHAR2(8) NOT NULL NUMBER(6) NUMBER(2) NUMBER(8.OE Schema Table 5–12 OE.2) NUMBER(6) NUMBER(6) Column Name ORDER_ID ORDER_DATE ORDER_MODE CUSTOMER_ID ORDER_STATUS ORDER_TOTAL SALES_REP_ID PROMOTION_ID Table 5–15 OE.CUSTOMERS Table Description Null? NOT NULL NOT NULL NOT NULL Type NUMBER(6) VARCHAR2(20) VARCHAR2(20) CUST_ADDRESS_TYP PHONE_LIST_TYP VARCHAR2(3) VARCHAR2(30) NUMBER(9.SDO_GEOMETRY DATE VARCHAR2(20) VARCHAR2(1) VARCHAR2(20) Column Name CUSTOMER_ID CUST_FIRST_NAME CUST_LAST_NAME CUST_ADDRESS PHONE_NUMBERS NLS_LANGUAGE NLS_TERRITORY CREDIT_LIMIT CUST_EMAIL ACCOUNT_MGR_ID CUST_GEO_LOCATION DATE_OF_BIRTH MARITAL_STATUS GENDER INCOME_LEVEL Table 5–13 OE.INVENTORIES Table Description Null? NOT NULL NOT NULL NOT NULL Type NUMBER(6) NUMBER(3) NUMBER(8) Column Name PRODUCT_ID WAREHOUSE_ID QUANTITY_ON_HAND Table 5–14 OE.2) VARCHAR2(30) NUMBER(6) MDSYS.

2) NUMBER(8) Table 5–16 OE.2) VARCHAR2(50) Column Name PRODUCT_ID PRODUCT_NAME PRODUCT_DESCRIPTION CATEGORY_ID WEIGHT_CLASS WARRANTY_PERIOD SUPPLIER_ID PRODUCT_STATUS LIST_PRICE MIN_PRICE CATALOG_URL Table 5–18 OE.) OE.WAREHOUSES Table Description Null? NOT NULL Type NUMBER(3) SYS.PM Schema Table 5–15 (Cont. Table 5–19 on page 5-11 lists the OE scripts in alphabetical order.2) NUMBER(8.XMLTYPE VARCHAR2(35) NUMBER(4) MDSYS. while Table 5–20 on page 5-11 lists its objects.ORDER_ITEMS Table Description Column Name LINE_ITEM_ID PRODUCT_ID UNIT_PRICE QUANTITY Null? NOT NULL NOT NULL Type NUMBER(3) NUMBER(6) NUMBER(8.PRODUCT_DESCRIPTIONS Table Description Null? NOT NULL NOT NULL NOT NULL Type NUMBER(6) VARCHAR2(3) NVARCHAR2(50) NVARCHAR2(2000) Column Name PRODUCT_ID LANGUAGE_ID TRANSLATED_NAME TRANSLATED_DESCRIPTION NOT NULL Table 5–17 OE. Note that the 5-10 Sample Schemas .SDO_GEOMETRY Column Name WAREHOUSE_ID WAREHOUSE_SPEC WAREHOUSE_NAME LOCATION_ID WH_GEO_LOCATION PM Schema This section lists the names of the scripts that create the Product Media (PM) schema and describes the objects in the schema.PRODUCT_INFORMATION Table Description Null? NOT NULL Type NUMBER(6) VARCHAR2(50) VARCHAR2(2000) NUMBER(2) NUMBER(1) INTERVAL YEAR(2) TO MONTH NUMBER(6)) VARCHAR2(20) NUMBER(8.

sql. SYS_ LOB0000045882C00071$$. SYS_LOB0000045882C00069$$. pm_p_lob. as follows: ■ ■ Table 5–21. TEXTDOC_TAB. you should first edit the path names in this file. SYS_ LOB0000045907C00003$$.sql PM Schema Scripts Description Gathers statistics on the PM objects Creates the PM objects Drops the PM schema and all its objects pm_p_ord.ORDIMAGE ORDSYS.sql pm_drop.ORDDOC Table 5–21 Column Name PRODUCT_ID PRODUCT_PHOTO PRODUCT_PHOTO_SIGNATURE PRODUCT_THUMBNAIL PRODUCT_VIDEO PRODUCT_AUDIO PRODUCT_TEXT PRODUCT_TESTIMONIALS Sample Schema Scripts and Object Descriptions 5-11 . TEXTDOC_TYP Table Type PM Table Descriptions This section describes the columns of each table of the PM schema.sql pm_cre. " PM. SYS_ LOB0000045907C00009$$.dat pm_main. Before attempting to load the data in a different environment. SYS_C003538 SYS_LOB0000045882C00003$$. SYS_ LOB0000045882C00019$$. SYS_LOB0000045907C00006$$. PRINTMEDIA_PK.ctl.PM Schema SQL*Loader data file pm_p_lob.sql Main script for the PM schema that calls other scripts Table 5–20 Object Type Index Lob PM Objects Objects ONLINEMEDIA_PK.ONLINE_MEDIA Table Description Null? NOT NULL Type NUMBER(6) ORDSYS. SYS_LOB0000045882C00034$$.ONLINE_MEDIA Table Description" on page 5-11 PM. " PM.sql.ONLINE_MEDIA Table Description" on page 5-11 Table 5–21. SYS_ LOB0000045882C00042$$. PRINT_MEDIA ADHEADER_TYP.ORDAUDIO CLOB ORDSYS.ORDVIDEO ORDSYS.dat contains hard-coded absolute path names that have been set during installation. SYS_LOB0000045907C00004$$.ORDIMAGESIGNATURE ORDSYS. pm_p_lob. SYS_LOB0000045882C00080$$. SYS_ LOB0000045882C00062$$. Populates the objects in the schema pm_p_lob. SYS_ LOB0000045908C00004$$ ONLINE_MEDIA. SYS_LOB0000045882C00017$$.ORDIMAGE ORDSYS. SYS_LOB0000045907C00015$$. SYS_ LOB0000045907C00005$$. SYS_LOB0000045882C00054$$. Table 5–19 Script Name pm_analz.

SYS_LOB0000045941C00029$$ AQ$_ORDERS_QUEUETABLE_E. SYS_ IOT_TOP_45932. disables. SYS_C003543. calls other scripts Enables. SYS_IOT_TOP_45951. ORDERS_QUEUE. and verifies IX objects Table 5–24 Object Type IX Objects Objects AQ$_ORDERS_QUEUETABLE_V. AQ$_STREAMS_QUEUE_TABLE_E.sql ix_main. STREAMS_QUEUE_N.IX Schema Table 5–22 PM. AQ$_STREAMS_QUEUE_TABLE_V SYS_C003540. Table 5–23 on page 5-12 lists the IX scripts in alphabetical order.sql dix_v3. ORDERS_QUEUE_R. SYS_ IOT_TOP_45939. while Table 5–24 on page 5-12 lists its objects. SYS_C003551. SYS_IOT_TOP_45949.PRINT_MEDIA Table Description Null? NOT NULL NOT NULL Type NUMBER(6) NUMBER(6) BLOB CLOB CLOB NCLOBO TEXTDOC_TAB BLOB BINARY FILE LOB ADHEADER_TYP Column Name PRODUCT_ID AD_ID AD_COMPOSITE AD_SOURCETEXT AD_FINALTEXT AD_FLTEXTN AD_TEXTDOCS_NTAB AD_PHOTO AD_GRAPHIC AD_HEADER IX Schema This section lists the names of the scripts that create the Information Exchange (IX) schema group and describes the objects in the schemas. STREAMS_QUEUE ORDERS_QUEUE_N.sql Information Exchange (IX) Schema Scripts Description Creates the IX schema objects Drops the IX schema objects Main script for the IX schema.sql vix_v3. STREAMS_ QUEUE_R AQ$_ORDERS_QUEUETABLE_N. SYS_ IOT_TOP_45953. STREAMS_QUEUE_TABLE ORDER_EVENT_TYP Evaluation Context Index Lob Queue Rule Set Sequence Table Type 5-12 Sample Schemas . Table 5–23 Script Name cix_v3. SYS_IOT_TOP_45934. SYS_C003548. SYS_IOT_TOP_45936. AQ$_STREAMS_QUEUE_TABLE_N ORDERS_QUEUETABLE. SYS_LOB0000045941C00028$$. SYS_IOT_TOP_45956 SYS_LOB0000045926C00036$$.

" IX.STREAMS_QUEUE_TABLE Table Description" on page 5-14 IX. AQ$STREAMS_QUEUE_TABLE_R. AQ$STREAMS_QUEUE_TABLE.ORDERS_QUEUETABLE Table Description Null? Type VARCHAR2(30) NOT NULL RAW(16) VARCHAR2(128) NUMBER NUMBER TIMESTAMP(6) NUMBER TIMESTAMP(6) NUMBER NUMBER NUMBER NUMBER TIMESTAMP(6) VARCHAR2(30) VARCHAR2(30) TIMESTAMP(6) VARCHAR2(30) VARCHAR2(30) NUMBER VARCHAR2(30) VARCHAR2(30) NUMBER NUMBER RAW(16) VARCHAR2(30) VARCHAR2(1024) NUMBER Table 5–25 Column Name Q_NAME MSGID CORRID PRIORITY STATE DELAY EXPIRATION TIME_MANAGER_INFO LOCAL_ORDER_NO CHAIN_NO CSCN DSCN ENQ_TIME ENQ_UID ENQ_TID DEQ_TIME EEQ_UID DEQ_TID RETRY_COUNT EXCEPTION_QSCHEMA EXCEPTION_QUEUE STEP_NO RECIPIENT_KEY DEQUEUE_MSGID SENDER_NAME SENDER_ADDRESS SENDER_PROTOCOL Sample Schema Scripts and Object Descriptions 5-13 .ORDERS_QUEUETABLE Table Description" on page 5-13 Table 5–26. AQ$ORDERS_QUEUETABLE_S. AQ$STREAMS_QUEUE_TABLE_S IX Table Descriptions This section describes the columns of each table of the IX schema. AQ$ORDERS_QUEUETABLE_R. " IX.IX Schema Table 5–24 (Cont.) IX Objects Object Type View Objects AQ$ORDERS_QUEUETABLE. as follows: ■ ■ Table 5–25.

) IX.ANYDATA Column Name Q_NAME MSGID CORRID PRIORITY STATE DELAY EXPIRATION TIME_MANAGER_INFO LOCAL_ORDER_NO CHAIN_NO CSCN DSCN ENQ_TIME ENQ_UID ENQ_TID DEQ_TIME EEQ_UID DEQ_TID RETRY_COUNT EXCEPTION_QSCHEMA EXCEPTION_QUEUE STEP_NO RECIPIENT_KEY DEQUEUE_MSGID SENDER_NAME SENDER_ADDRESS SENDER_PROTOCOL USER_DATA USER_PROP 5-14 Sample Schemas .ORDERS_QUEUETABLE Table Description Column Name USER_DATA USER_PROP Null? Type ORDER_EVENT_TYP SYS.ANYDATA Table 5–26 IX.IX Schema Table 5–25 (Cont.STREAMS_QUEUE_TABLE Table Description Null? Type VARCHAR2(30) NOT NULL RAW(16) VARCHAR2(128) NUMBER NUMBER TIMESTAMP(6) NUMBER TIMESTAMP(6) NUMBER NUMBER NUMBER NUMBER TIMESTAMP(6) VARCHAR2(30) VARCHAR2(30) TIMESTAMP(6) VARCHAR2(30) VARCHAR2(30) NUMBER VARCHAR2(30) VARCHAR2(30) NUMBER NUMBER RAW(16) VARCHAR2(30) VARCHAR2(1024) NUMBER ORDER_EVENT_TYP SYS.

COSTS_TIME_BIX. SYS_IOT_TOP_45932. " SH. PROMO_PK. SALES PROFITS Index Partition Lob Materialized View Table Table Partition View SH Table Descriptions This section describes the columns of each table of the IX schema.sql sh_cremv. SALES_CHANNEL_BIX. SALES. PROMOTIONS. " SH. PRODUCTS_ PROD_CAT_IX. FW_ PSC_S_MV_CHAN_BIX. CUSTOMERS_GENDER_BIX. SALES_PROD_BIX.sql sh_idx. DR$SUP_TEXT_IDX$X. SALES_PROMO_BIX. COSTS_TIME_BIX.sql olp_v3.SH Schema SH Schema This section lists the names of the scripts that create the Sales History (SH) schema and describes the objects in the schema. Table 5–27 Script Name sh_analz. PRODUCTS. FW_PSC_S_MV_ SUBCAT_BIX. SALES_CHANNEL_BIX.sql sh_olp_d. CUSTOMERS_YOB_BIX. FW_PSC_S_MV_WD_BIX.sql SH Schema Scripts Description Gathers statistics on the schema objects Creates comments for the objects in the schema Modifies constraints on objects in the schema Creates the objects in the schema Creates materialized views and bitmapped indexes Drops the SH schema and all its objects Creates indexes on tables in the schema Main script for the SH schema. SALES_PROD_BIX.sql sh_cre. as follows: ■ ■ Table 5–29. TIMES_DIM CHANNELS_PK. CUSTOMERS_PK. SALES_ CUST_BIX.sql sh_comnt. PRODUCTS_PK. TIMES_PK COSTS_PROD_BIX.COSTS Table Description" on page 5-16 Sample Schema Scripts and Object Descriptions 5-15 . CUSTOMERS_DIM. PRODUCTS_DIM.CHANNELS Table Description" on page 5-16 Table 5–30. SYS_IOT_TOP_45927. SALES_CUST_BIX. PRODUCTS_PROD_ SUBCAT_IX. SALES_PROMO_BIX. COSTS. CUSTOMERS. COSTS_PROD_BIX. COUNTRIES.sql sh_drop. PROMOTIONS_ DIM. SALES_TIME_ BIX SYS_LOB0000045924C00006$$. Table 5–27 on page 5-15 lists the SH scripts in alphabetical order. TIMES COSTS. while Table 5–28 on page 5-15 lists its objects.sql sh_main. SALES_TIME_BIX. calls other scripts Creates dimensions and hierarchies used by the OLAP server Drops the objects used by the OLAP server Table 5–28 Object Type Dimension Index SH Objects Objects CHANNELS_DIM. FWEEK_PSCAT_SALES_MV CHANNELS. COUNTRIES_ PK. CUSTOMERS_MARITAL_BIX.sql sh_cons. PRODUCTS_PROD_STATUS_BIX. SYS_LOB0000045929C00002$$ CAL_MONTH_SALES_MV. FW_PSC_S_MV_PROMO_BIX. SUP_ TEXT_IDX.

PROMOTIONS Table Description" on page 5-18 Table 5–35.2) Column Name PROD_ID TIME_DESC PROMO_ID CHANNEL_ID UNIT_COST UNIT_PRICE Table 5–31 SH.COSTS Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type NUMBER DATE NUMBER NUMBER NUMBER(10. " SH.PRODUCTS Table Description" on page 5-17 Table 5–34. " SH.COUNTRIES Table Description" on page 5-16 Table 5–32.COUNTRIES Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type NUMBER CHAR(2) VARCHAR2(40) VARCHAR2(30) NUMBER VARCHAR2(20) NUMBER VARCHAR2(11) NUMBER VARCHAR2(40) Column Name COUNTRY_ID COUNTRY_ISO_CODE COUNTRY_NAME COUNTRY_SUBREGION COUNTRY_SUBREGION_ID COUNTRY_REGION COUNTRY_REGION_ID COUNTRY_TOTAL COUNTRY_TOTAL_ID COUNTRY_NAME_HIST 5-16 Sample Schemas . " SH.2) NUMBER(10. " SH.SALES Table Description" on page 5-18 Table 5–36.CUSTOMERS Table Description" on page 5-17 Table 5–33. " SH. " SH.CHANNELS Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type NUMBER VARCHAR2(20) VARCHAR2(20) NUMBER VARCHAR2(13) NUMBER Table 5–29 Column Name CHANNEL_ID CHANNEL_DESC CHANNEL_CLASS CHANNEL_CLASS_ID CHANNEL_TOTAL CHANNEL_TOTAL_ID Table 5–30 SH.SH Schema ■ ■ ■ ■ ■ ■ Table 5–31.TIMES Table Description" on page 5-19 SH.

CUSTOMERS Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type NUMBER VARCHAR2(20) VARCHAR2(40) CHAR(1) NUMBER(4) VARCHAR2(20) NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL VARCHAR2(40) VARCHAR2(10) VARCHAR2(30) NUMBER VARCHAR2(40) NUMBER NUMBER VARCHAR2(25) VARCHAR2(30) NUMBER VARCHAR2(30) NOT NULL NOT NULL VARCHAR2(14) NUMBER NUMBER DATE DATE VARCHAR2(1) Column Name CUST_ID CUST_FIRST_NAME CUST_LAST_NAME CUST_GENDER CUST_YEAR_OF_BRITH CUST_MARITAL_STATUS CUST_STREET_ADDRESS CUST_POSTAL_CODE CUST_CITY CUST_CITY_ID CUST_STATE_PROVINCE CUST_STATE_PROVINCE_ID COUNTRY_ID CUST_MAIN_PHONE_NUMBER CUST_INCOME_LEVEL CUST_CREDIT_LIMIT CUST_EMAIL CUST_TOTAL CUST_TOTAL_ID CUST_SRC_ID CUST_EFF_FROM CUST_EFF_TO CUST_VALID Table 5–33 SH.PRODUCTS Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type NUMBER(6) VARCHAR2(50) VARCHAR2(4000) VARCHAR2(50) NUMBER VARCHAR2(2000) VARCHAR2(50) NUMBER VARCHAR2(2000) NUMBER(3) VARCHAR2(20) Column Name PROD_ID PROD_NAME PROD_DESC PROD_SUBCATEGORY PROD_SUBCATEGORY_ID PROD_SUBCATEGORY_DESC PROD_CATEGORY PRD_CATEGORY_ID PROD_CATEGORY_DESC PROD_WEIGHT_CLASS PROD_UNIT_OF_MEASURE Sample Schema Scripts and Object Descriptions 5-17 .SH Schema Table 5–32 SH.

2) Column Name PROD_ID CUST_ID TIME_ID CHANNEL_ID PROMO_ID QUANTITY_SOLD AMOUNT_SOLD 5-18 Sample Schemas .PROMOTIONS Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type NUMBER(6) VARCHAR2(30) VARCHAR2(30) NUMBER VARCHAR2(30) NUMBER NUMBER(10.PRODUCTS Table Description Column Name PRD_PACK_SIZE PROD_SUPPLIER_ID PROD_STATUS PROD_LIST_PRICE PRD_MIN_PRICE PROD_TOTAL PROD_TOTAL_ID PROD_SRC_ID PRD_EFF_FROM PROD_EFF_TO PROD_VALID Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type VARCHAR2(30) NUMBER(6) VARCHAR2(20) NUMBER(8.2) NUMBER(8.2) VARCHAR2(13) NUMBER NUMBER DATE DATE VARCHAR2(1) Table 5–34 SH.) SH.2) DATE DATE VARCHAR2(15) NUMBER Column Name PROMO_ID PROMO_NAME PROMO_SUBCATEGORY PROMO_SUBCATEGORY_ID PROMO_CATEGORY PRMO_CATEGORY_ID PROMO_COST PROMO_BEGIN_DATE PROMO_END_DATE PROMO_TOTAL PROMO_TOTAL_ID Table 5–35 SH.2) NUMBER(10.SH Schema Table 5–33 (Cont.SALES Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type NUMBER NUMBER DATE NUMBER NUMBER NUMBER(10.

TIMES Table Description Null? NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Type DATE VARCHAR2(9) NUMBER(1) NUMBER(2) NUMBER(2) NUMBER(2) DATE NUMBER NUMBER(2) NUMBER(2) VARCHAR2(8) NUMBER VARCHAR2(8) NUMBER NUMBER NUMBER DATE DATE VARCHAR2(9) VARCHAR2(9) CHAR(7) NUMBER CHAR(7) NUMBER NUMBER NUMBER DATE DATE NUMBER(1) NUMBER(1) NUMBER(4) NUMBER NUMBER(4) NUMBER NUMBER NUMBER Column Name TIME_ID DAY_NAME DAY_NUMBER_IN_WEEK DAY_NUMBER_IN_MONTH CALENDAR_WEEK_NUMBER FISCAL_WEEK_NUMBER WEEK_ENDING_DAY WEEK_ENDING_DAY_ID CALENDAR_MONTH_NUMBER FISCAL_MONTH_NUMBER CALENDAR_MONTH_DESC CALENDAR_MONTH_ID FISCAL_MONTH_DESC FISCAL_MONTH_ID DAYS_IN_CAL_MONTH DAYS_IN_FIS_MONTH END_OF_CAL_MONTH END_OF_FIS_MONTH CALENDAR_MONTH_NAME FISCAL_MONTH_NAME CALENDAR_QUARTER_DESC CALENBDAR_QUARTER_ID FISCAL_QUARTER_DESC FISCAL_QUARTER_ID DAYS_IN_CAL_QUARTER DAYS_IN_FIS_QUARTER END_OF_CAL_QUARTER END_OF_FIS_QUARTER CALENDAR_QUARTER_NUMBER NOT NULL FISCAL_QUARTER_NUMBER CALENDAR_YEAR CALENDAR_YEAR_ID FISCAL_YEAR FISCAL_YEAR_ID DAYS_IN_CAL_YEAR DAYS_IN_FIS_YEAR NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL NOT NULL Sample Schema Scripts and Object Descriptions 5-19 .SH Schema Table 5–36 SH.

TIMES Table Description Column Name END_OF_CAL_YEAR END_OF_FIS_YEAR Null? NOT NULL NOT NULL Type DATE DATE 5-20 Sample Schemas .SH Schema Table 5–36 (Cont.) SH.

installing. 5-15 H HR schema general description. 2-1 IX schema general description. 2-4 OE schema general description. 2-2 of IX schema. 2-5 of OC subschema. 1 general description. 5-7 PM. 2-1 dependencies among schemas. 5-7 3-3 3-2 P PM schema Index-1 . 2-1 installation of Sample Schemas. 5-12 O OC subschema general description. 2-5 scripts. 5-1 SCOTT schema. 2-5 scripts. 2-4 of PM schema. 2-6 order of. 2-4 scripts. 2-3 3-1 5-1 I installation manual. 2-2 DEPT table. 5-10 R resetting the Sample Schemas. 2-2 using Database Configuration Assistant. 3-3 installing. Sample Schemas design principles. 3-3 installing. 2 general information. installing. 1 S Sample Schema scripts OE. 3-3 installing. 1 SH schema general description. 2-1 scripts master. general information. 5-10 scripts. installing. 2-7 E EMP table. 1 installing.Index D Database Configuration Assistant using to install Sample Schemas. of Sample Schemas. 2-6 scripts. 2-4 of OE schema. 2-5 of SH schema.

Index-2 .

Sign up to vote on this title
UsefulNot useful