I would highly recommend reading the Oracle Concepts Guide for information on how the Oracle database works, what its components are and some information on how to manage it. For more information on managing these concepts, see the Administrator's Guide. Both documents are ESSENTIAL reading for the Oracle DBA. I highly recommend that you read both of these cover to cover. And if you're like most of us, you will probably want to read these a couple of times as it might take a bit for things to sink in.
To me, a "schema" is a collection of objects to support your application. The schema is composed of tables, indexes, views, stored procedures, etc. All objects in the schema are owned by a user. You create that user with the CREATE USER command. After the user is created (and you have granted appropriate permissions to that user), you sign on to the database and create the schema objects. There are some who feel that creating the user creates the schema. I like to make a slightly different distinction as I feel a user with no objects is not really a schema, but all of the objects the user owns denotes the schema. Please read the documents described above and they will explain how you create users and create schema objects.Have a question for Brian Peasland? Send an e-mail to firstname.lastname@example.org.
Dig Deeper on Oracle DBA jobs, training and certification
Related Q&A from Brian Peasland
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs. Continue Reading
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command. Continue Reading
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming. Continue Reading