In Oracle, a user is synonymous with a schema. The user/schema can own many different types of objects (tables, indexes, views, procedures, triggers, etc.). Some of those objects require physical storage. For instance, data in a table and its indexes require space. Some objects do not require physical storage, like views and stored procedures. Oracle calls the objects that require space segments. A segment is physically located in one tablespace. A user is given a default tablespace but that user may be able to create a segment in any number of tablespaces. And many users may be allowed to store segments in the same tablespace. The tablespace is a logical container (made up of physical datafiles) used to store segments from one or many users. There is no real correlation to the user and the tablespace in this respect. A user does not own the tablespace and a user is not absolutely tied to any one tablespace.
Please read the Oracle Concepts document for your Oracle version as these concepts are fully explained there.
Dig Deeper on Oracle database backup and recovery
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
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.