- Install Oracle 11g On Linux
- How To Install Hr Sample Schema In Oracle 11g
- How To Install Sample Schemas In Oracle 11g Pdf
- How To Install Sample Schemas In Oracle 11g
- Oracle 11g Setup
Posted Jun 23, 2010
By Steve Callan
- How To Unlock Oe Schema In Oracle 11g Create a new set of BIPLATFORM and MDS schemas in the database using RCU (see For these reports to run correctly, unlock the OE sample schema.
- Installing The Oracle 10g Or Oracle 11g Sample Schemas >>>CLICK HERE.
Installing Oracle Database 11g XE and Unlocking the HR Sample Schema – A Tutorial with Screenshots When learning to develop Oracle Fusion applications, one of your first steps, if not already completed, should be to install a database for your applications to connect to.
Having a re-usable dump file for installing Oracle Database Sample Schemas is much more convenient than the current method. Would you rather download a compressed file containing one (or several) dump files, including a parameter file suitable for use during an import session or job or use the Oracle Universal Installer?
I wrote an introductory article a few years ago (actually more like six) about the new Oracle Database Sample Schemas you can have installed within a database. The installation method via Oracle Universal Installer has changed a little bit since then. Where and when you install a companion CD probably dissuaded users from even trying to install the schemas in the first place. In fact, if you didn't install the sample schemas in a newly created database (via DBCA) session, the work it would take to undo that decision (that is, do the install later) would be well, let's just say it is almost infinitely harder than it needs to be.
First and foremost, the official documentation for installing after the fact is outright wrong. The documentation references non-existent files and directories, and to make things worse, OTN contributes to the problem by providing watered down versions of (at least) the HR and OE schemas in some of the Oracle by Example modules. On some after-the-fact installations, a spatial data type within one table causes problems during the CREATE TABLE statement (error message about how the database does not support spatial datatypes).
Why not make the sample schemas one of two things (or even both); first, how about a complete zip file in and of itself, containing nothing more than all of the DDL and insert statements? This would be similar to what Microsoft does (or used to do, but another site maintains the files now) in terms of having you download a Windows MSI installer file for a particular database (AdventureWorks and its variations, to name one series of ready-to-go databases). Second, which is a more interesting approach that would reinforce feature usage and practical application, is to simply make the sample schemas a Data Pump export dump file. You could download a compressed file that when expanded would further contain either one dump file, or several dump files (one for each schema). Also included in the package would be a parameter file suitable for use during an import session or job.
With a single dump file and a starter-like parameter file, you would have the opportunity to edit the file for metadata filters (to INCLUDE or EXCLUDE schemas). You could also take care of tablespace mappings if your target database did not include a USERS or EXAMPLES tablespace. The simplicity and efficiency of this approach, compared to the current method (go download a half-GB file, install it into an existing Oracle home, start watching Oracle TV, aka OUI screenshots), and well, I'm sure you get the idea. The problem is that Oracle Corporation does not.
Just out of curiosity, when you do install Oracle right now, and when you get to the Database Configuration Assistant phase where the seed database is being created, where are the DDL and insert statements coming from? The point of the question is that we can deduce Oracle has a method of doing the schema creation and data population today, but it is not surfaced to us (the users) in a convenient or consistently accessible manner.
Virtually all code snippets and examples within the entire documentation collection for a release are based upon one or more of the sample schemas. The documentation and access to the sample schemas should go hand-in-hand as far as ease of access is concerned. I can see having the other somewhat less than mainstream example sets being installed under the current method. The two people who actually use XML DB, for example, probably aren't ever going to complain about what it takes to install XML DB examples. They're probably happy enough knowing the examples exist in the first place, now if we can only figure out what XML DB can be used for.
Yet another variation for installation, also reinforcing feature usage and exposure to relatively more advanced tasks would be to have the schemas contained within a standalone database file. How could you take a standalone data file and plug it into an existing database? Isn't that the whole idea of transportable tablespaces? So along with the datafile comes one other file, namely, the Data Pump export dump file of the tablespace's metadata.
To back up words with action, I'll get the ball rolling on this and post a dump file that can be downloaded here.
As a review of concepts, suppose you want to install the sample schemas in your Linux development environment. Knowing ahead of time that the dump file you download will have been generated on a Windows platform, is that going to matter to you? If you think so, why is that? Let's go back to pre-9i days, and all you have are original export and import. How did you do a platform migration back then? Export out with the lower version of Oracle's exp executable, whatever it was running on, and then import in with the newer version's imp executable? Where did the platform version come into play? It didn't, and it still doesn't.
It's what's in the dump file that matters, not which platform the file was created on. Or, at least not until we get to the transportable tablespace approach and the byte ordering of the file may matter, depending on the platforms involved. Aside from that one issue, Oracle doesn't care where the dump file was created because what is inside the file is the only thing matters.
The command and export parameter file are going to be as simple as this:
Export parameter file contents
In Closing
If Data Pump is new to you, take a look at the Oracle by Example demo of using Data Pump, available here. Having a re-usable dump file for installing the sample schemas is going to be much more convenient than the current method.
» See All Articles by Columnist Steve Callan
Latest Forum Threads | |||
Oracle Forum | |||
Topic | By | Replies | Updated |
Oracle Data Mining: Classification | jan.hasller | 0 | July 5th, 07:19 AM |
Find duplicates - Unique IDs | Lava | 5 | July 2nd, 08:30 AM |
no matching unique or primary key | rcanter | 1 | April 25th, 12:32 PM |
Update values of one table based on condition of values in other table using Trigger | Gladiator | 3 | February 29th, 06:01 PM |
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:
- Caution:By installing any of the Oracle Database 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. You should not use Oracle Database Sample Schemas for your personal or business data and applications. They are meant to be used for demonstration purposes only.
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:See Also:
'Guidelines for Securing Passwords' in Oracle Database Security Guide for guidelines related to creating secure passwordsThe 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 informationSchema 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:
- Create the
HR
schema. - Create the
OE
schema: TheHR
schema is already present, and you must know the password for theHR
schema to grantHR
object privileges toOE
. SomeHR
tables are visible to theOE
user with the use of private synonyms. In addition, someOE
tables have foreign key relationships toHR
tables. - Create the
PM
schema: Foreign key relationships require that theOE
schema already exist when thePM
schema is created. You must know the password forOE,
to grant toPM
the right to establish and use these foreign keys.Note:ThePM
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. - Create the
IX
schema: The information exchange schemaIX
is based on order entry data inOE
. Again, foreign key relationships require that theOE
schema already be present when theIX
schema is created. You must know the password forOE
to grant toIX
, the right to establish and use the foreign keys. - Create the
SH
schema. TheSH
schema logically depends on theOE
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:- You must connect as a system administrator using the
SYSDBA
privilege. - When prompted to enter a password for the schema, enter a secure password that meets the requirements described in Oracle Database Security Guide.
- 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
- 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:- Log on to SQL*Plus as
SYS
andconnect
using theAS SYSDBA
privilege. - To run the
hr_main.sql
script, use the following command: - Enter a secure password for HRSee Also:Oracle Database Security Guide for the minimum password requirements
- Enter an appropriate tablespace, for example,
users
as the default tablespace forHR
- Enter
temp
as the temporary tablespace forHR
- Enter your
SYS
password - Enter the directory path, for example,
$ORACLE_HOME
/demo/schema/log/
, for your log directory
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:Running
hr_main.sql
accomplishes the following tasks:- 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, 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:- 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
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: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:- 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.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: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:- Prompts for passwords and tablespace names used within the scripts
- Removes any previously installed
IX
schema Mdac for windows 7. - 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.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: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:- 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.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:For a complete listing of the scripts and their functions, refer to Table 5-27.
Cracked skin on fingers, teatree oil. Happy solution for cracked fingertips. In less than two days my skin had healed with no signs of it being prone to cracking again. I keep pressing my fingertips in expectation of the stinging or pain, so I can make a mental note which finger to be careful with, but there is nothing. Did you just put straight tea tree oil on your. Washing of hands tends to wash off the natural oil generated by the sebaceous glands of the skin, which in turn makes the skin dryer and more prone to cracked fingertips. Local application of moisturizers tends to reduce the dryness of the skin and hasten the process of healing. The problem with extremely unhealthy and cracked skin is that it can’t hold on to protective oils in the stratum corneum, and water escapes. Tea Tree Essential Oil. 7 thoughts on “ Tea Tree Heel Cream for Extremely Cracked Heels ” christa sterken. 13 May, 2014 at 11:51 pm.
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:
Install Oracle 11g On Linux
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:mkverify.log
is the Sample Schema creation log file.hr_main.log
is theHR
schema creation log file.oe_oc_main.log
is theOE
schema creation log file.pm_main.log
is thePM
schema creation log file.pm_p_lob.log
is the SQL*Loader log file forPM.PRINT_MEDIA
.ix_main.log
is theIX
schema creation log file.sh_main.log
is theSH
schema creation log file.cust.log
is the SQL*Loader log file forSH.CUSTOMERS
.prod.log
is the SQL*Loader log file forSH.PRODUCTS
.promo.log
is the SQL*Loader log file forSH.PROMOTIONS
.sales.log
is the SQL*Loader log file forSH.SALES
.sales_ext.log
is the external table log file forSH.COSTS
.
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:How To Install Hr Sample Schema In Oracle 11g
- Connect as the user
OE
. - Run the
oc_drop.sql
. script. - Connect as
SYSTEM
. - Ensure that no user is connected as
OE
: - Drop the user:
For the
IX
schemas:How To Install Sample Schemas In Oracle 11g Pdf
- Connect as
SYSTEM
. - Ensure that no user is connected as an
IX
user: - Drop the schemas by running the
dix.sql
. script. You will be prompted for passwords for the individual users.
Uninstalling Sample Schemas
How To Install Sample Schemas In Oracle 11g
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.Oracle 11g Setup
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.