Turn: What does the schema in Oracle refer to?

It seems that some people still do not understand the true meaning of the schema, and now I have to tidy up a bit, I hope to help you.

Let's start by looking at their definition:
ASchemais a collection of the database objects (used by a user.).
Schema ObjectsIs the logical structures that directly refer to the database ' s data.
AUseris a name defined in the database that can connect to and Access objects.
Schemas and UsersHelp database administrators manage database security.

From the definition we can see that the schema is a collection of database objects, in order to distinguish between the collection, we need to give this collection a name, these are the many similar user names that we see under the Enterprise Manager Scheme node, these are similar to the user name of the node is actually a schema, The schema contains various objects such as tables, views, sequences, stored procedures, synonyms, indexes, clusters, and database links.

A user typically corresponds to a schema, the user's schema name equals the user name, and is used as the default schema for that user. This is why we see the schema name as the database username under the Enterprise Manager scenario. The Oracle database cannot create a new schema, and to create a schema, it can only be solved by creating a user's method (although Oracle has the CREATE SCHEMA statement, it is not used to create a schema) Create a user with a schem that has the same name as the user name and act as the default shcema for that user. That is, the number of schemas is the same as the number of user, and the schema name corresponds to the user name one by one and the same, all we can call the schema as the user alias, although this is not accurate, but it is easier to understand some.

A user has a default schema, whose schema name is equal to the user name, and of course a user can use other schemas. If we visit a table and do not indicate which schema the table belongs to, the system automatically adds the default Sheman name to the table. For example, when we access the database, we access the EMP table under the Scott user, through the select * from EMP; In fact, the complete syntax for this SQL statement is select * from Scott.emp. The full name of an object in the database is Schema.object, not user.object. Similar if we do not specify the schema of the object when creating the object, the schema of the object is the user's default schema. This is like a user with a default tablespace, but the user can also use other tablespaces, and if we do not specify a tablespace when we create the object, the object is stored in the default tablespace, and in order for the object to be stored in another table space, we need to specify the table space for the object when it is created.

Cough, say so much, give everybody an example, otherwise, everything is dull!
Sql> Gruant DBA to Scott

Sql> CREATE TABLE Test (name char (10));
Table created.

Sql> CREATE TABLE System.test (name char (10));
Table created.

sql> INSERT into test values (' Scott ');
1 row created.

sql> INSERT into system.test values (' system ');
1 row created.

Sql> commit;
Commit complete.

Sql> Conn System/manager
Connected.

Sql> select * from test;
NAME
----------
System

sql> ALTER SESSION SET current_schema = Scott; --Change user Default schema name
Session altered.

Sql> select * from test;
NAME
----------
Scott

Sql> Select owner, table_name from Dba_tables where Table_name=upper (' test ');
OWNER table_name
------------------------------ ------------------------------
SCOTT TEST
SYSTEM TEST
The above query is the basis for me to say that the schema is the alias of the user. In fact, in use, Shcema is exactly the same as the user, there is no difference, the user name can appear where the schema name appears.

Turn: What does the schema in Oracle refer to?