I always confuse the concept of TableSpaces and Schema. So I make up my mind to understand them today. The following is the definition of them, which come from http://www.ss64.com/ora/index.html
Schema:
A schema is a set of objects owned by a user, A user automatically has all object privileges for schema objects contained in his or her schema. A user can grant any object privilege on any schema object he or she owns to any other user or role.
A privilege can be granted explicitly. For example, the privilege to insert records into the EMP table can be explicitly granted to the user SCOTT.
Alternatively a privilege can be granted to a role (a named group of privileges), and then the role can be granted to one or more users.
For example, the privilege to insert records into the EMP table can be granted to the role named CLERK, which in turn can be granted to the users SCOTT and BRIAN.
-----------------------------------------------------------------------------
TableSpaces
A tablespace is a logical storage unit - multiple application objects (e.g. tables) can be stored in one tablespace. A database can contain multiple tablespaces.
A tablespace can be online or offline (not accessible), and can contain one or more datafiles, each of which can be online or offline.
There is no relationship between a tablespace and a schema. Objects in the same schema can be in different tablespaces, and a tablespace can hold objects from different schemas.
A tablespace can be set to read-only to eliminate the need to perform backup and recovery of large, static portions of the database.
A tablespace can be set to temporary to optimise the storage of temporary objects.
Tablespaces can use one of two methods to keep track of free and used space: Dictionary-managed or Locally managed - this is chosen when the tablespace is created and cannot be altered at a later date.
[@more@]来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/8454401/viewspace-895888/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/8454401/viewspace-895888/